refactor: rename b00t-py -> b00t-pyverse (PyPI naming collision) - #892
Merged
Conversation
b00t-py/b00t_py was rejected by PyPI ("too similar to an existing
project") — a genuine collision with the pre-existing, unrelated
boot-py/boot.py package (leetspeak 0-vs-o similarity). Renamed the crate,
Python import package, and every reference across the repo to
b00t-pyverse/b00t_pyverse:
- b00t-py/ -> b00t-pyverse/ (git mv, history preserved)
- python/b00t_py/ -> python/b00t_pyverse/
- tests/test_b00t_py.py -> tests/test_b00t_pyverse.py
- Cargo.toml: [package] name, [lib] name
- pyproject.toml: [project] name = "b00t-pyverse", module-name = "b00t_pyverse._core"
- src/lib.rs: create_exception! module path, doc comments
- workspace Cargo.toml: member path
- b00t-j0b-py (real consumer — genuinely imports and calls into this
package): both source files updated via `import b00t_pyverse as b00t_py`
so the many internal b00t_py.func(...) call sites didn't all need
touching, plus user-facing error/docstring text
- Dockerfile.b00t-cli, b00t-azure-cp/Dockerfile: COPY paths (would have
broken the image build otherwise)
- _b00t_/*.skill.tomllm + skills/*/SKILL.md pairs, .claude-plugin/README.md,
.opencode context, PRD-ARCH-014/015 datums: living reference docs and
code examples
- _b00t_/learn/b00t-py.md -> b00t-pyverse.md: corrected, not just renamed —
it had documented the actual bug (importing "b00t_py.b00t_py" instead of
"b00t_py._core") as if it were the fix
Left alone: docs/superpowers/plans/2026-05-02-*.md (dated historical
record, not living documentation).
Verified fully operational under the new name: maturin build --release
succeeds (abi3 wheel, b00t_pyverse-0.10.2-cp38-abi3-*.whl), fresh venv
install works, full test suite 17/17 passes, README Quick Start example
run verbatim and confirmed accurate, twine check passes, and
`cargo check -p b00t-cli --lib` confirms the workspace member rename in
root Cargo.toml didn't break the rest of the workspace.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
b00t-py/b00t_pywas rejected by PyPI as "too similar to an existing project" — a genuine collision with the pre-existing, unrelatedboot-py/boot.pypackage (leetspeak 0-vs-o similarity check).b00t-pyverse/b00t_pyverse(directorygit mv'd, history preserved).b00t_py.b00t_pyvs the actual builtb00t_py._core), a hardcoded stale__version__string instead of the canonical workspace version, and a test file hardcoded to a Python 3.13.sofilename that never matched any installed interpreter. Also added theabi3-py38PyO3 feature so one wheel now works across Python 3.8+ instead of needing a rebuild per minor version.b00t-j0b-py, which genuinelyimports and calls into this package) viaimport b00t_pyverse as b00t_pyso its many internal call sites didn't all need touching, plus its user-facing error/docstring text.Dockerfile.b00t-cli,b00t-azure-cp/DockerfileCOPYpaths) and living reference docs (_b00t_/*.skill.tomllm+skills/*/SKILL.mdpairs,.claude-plugin/README.md, opencode context,PRD-ARCH-014/015datums). Left the one dated historical plan doc alone._b00t_/learn/b00t-py.md→b00t-pyverse.md, which had documented the actual bug as if it were the fix.Test plan
maturin build --releasesucceeds — producesb00t_pyverse-0.10.2-cp38-abi3-manylinux_2_35_x86_64.whlpytest tests/→ 17/17 passedtwine checkpassescargo check -p b00t-cli --libconfirms the workspace member rename in rootCargo.tomldidn't break the rest of the workspaceb00t_py/b00t-pyreferences outside the two files that intentionally alias it (import b00t_pyverse as b00t_py) and Cargo.lock (regenerates)🤖 Generated with Claude Code