← ClaudeAtlas

python-versioninglisted

Use when deciding what version a Python distribution declares and what changes it — a first release, a breaking change, a deprecation, a pre-release, a tag, or the note a consumer reads before upgrading. Owns whether the number is a compatibility promise at all or only a label, the single place it is declared, which change forces which bump, what 0.y.z deliberately withholds, and the canonical form a published version must already be in before a build tool rewrites it silently. What a package root re-exports is `python-packaging`'s, retiring a published identifier is `naming`'s, and choosing a version floor for a dependency this project consumes is the inverse concern and belongs to `python-toolchain`.
wntic/pyhouse · ★ 3 · AI & Automation · score 76
Install: claude install-skill wntic/pyhouse
# Python Versioning — what the number promises, and what changes it The version a distribution declares, the change that moves it, and the tag and note that make it reachable. **The number is a claim about compatibility**, so this skill is about the claim first and the digits second. What the compatible surface actually consists of is `python-packaging`'s; this skill owns what happens to the number when that surface changes. **Precondition — something chooses which version to install.** Which rules bind follows from who reads the number, not from how the project is built: | Does anything… | If no, these do not apply | |---|---| | depend on this by a version range, or install it from an index | rules 6, 7, 8, 9 — no one can be broken by a bump nobody reads | | have a declared public surface | rules 6, 7, 8 — there is no promise for a change to break | | publish to an index that refuses re-uploads | rule 11 — a mistake is corrected in place, not outlived | | ship its members as separate artifacts | rule 13 — one artifact, one number | **Rules 1, 2, 3, 4, 5, 10, 12, 14 and 15 hold for any distribution at all**, including one deployed from a commit and installed by nothing. A service that is built from `main` and run in a container has no consumer choosing a version, so its number is a **label** rather than a promise — it still has to be single-sourced, canonical and tagged, so a running artifact can be traced back to a tree, and that is all. Wherever a number moves at all, t