You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
release bump should either automatically update or remind to update README version to x.y.z+ #169
PEP 101 talks about manually updating the top-level README.rst file to the new version in the final steps (bump) of the release process as part of the post-release commit. In the past, release managers manually updated the version in the README to 3.x.y+ (i.e. 3.12.6+) to match the PY_VERSION string automatically updated in Include/patchlevel.h that is displayed by sys.version and the REPL. That makes it clearer that the repo does not necessarily reflect the state of any particular release - a checkout of the release tag (v3.12.6) provides that - but rather something newer than a release. I think PEP 101 used to explicitly mention this but it certainly would be better to automate if possible.
❯ rg "This is Python version" --sort-files3.10/README.rst1:This is Python version 3.10.203.11/README.rst1:This is Python version 3.11.153.12/README.rst1:This is Python version 3.12.133.13/README.rst1:This is Python version 3.13.143.14/README.rst1:This is Python version 3.14.63.15/README.rst1:This is Python version 3.15.0 beta 3main/README.rst1:This is Python version 3.16.0 alpha 0
If we were to add + (or +dev for 3.15 and later), that works cleanly for fully released 3.10 to 3.14, but not so much for pre-releases; would 3.15 read "This is Python version 3.15.0 beta 3+dev"?
Some ideas:
as above: "This is Python version 3.15.0 beta 3+dev"
switch to the short form: "This is Python version 3.15.0b3+dev"
ditch the micro and alpha/beta/RC: "This is Python version 3.15" or "This is Python 3.15"
I think either option 1 or 2 is fine; the text doesn't have to exactly match the displayed version info in the build. What's more important is having the README be clear that this is not a tagged / released snapshot so -1 for option 3. (Same for the built docs, for that matter.)
Activity
hugovk commentedon Jul 7, 2026
Right now:
If we were to add
+(or+devfor 3.15 and later), that works cleanly for fully released 3.10 to 3.14, but not so much for pre-releases; would 3.15 read "This is Python version 3.15.0 beta 3+dev"?Some ideas:
ned-deily commentedon Jul 7, 2026
I think either option 1 or 2 is fine; the text doesn't have to exactly match the displayed version info in the build. What's more important is having the README be clear that this is not a tagged / released snapshot so -1 for option 3. (Same for the built docs, for that matter.)