-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cpython#121277: Replace next
versions in docs by the just-released version
#164
Conversation
Dear RMs, do you want this? I can add tests for the remaining uncovered lines; is this the style of tests you're looking for? |
Yes, I think so, but still need to take a closer look, and would also like to hear from other RMs who have actually made releases :)
I've not had a proper look yet, but will do. |
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, I tested it against python/cpython#121278 and it worked as expected.
Here's a few small suggestions.
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
On the sprint, @Yhg1s agreed to the concept, so I'll merge. I'll link related PRs on the CPython issue: python/cpython#121277 |
See CPython issue: python/cpython#121277
After the CPython PR is merged, a Sphinx plugin will expand
next
in directives likeversionchanged
to e.g.3.14.0b0 (unreleased)
.This PR gives the RM a tool to replace all such occurences of
next
by the currently released version, baking it directly into the ReST source files, as part of the version bump commit.This is done textually (I don't know of a round-trip parser for ReST).
To make sure the text manipulation worked, the released docs artifact (if it's being published) is grepped for the string
(unreleased)
, and if it's found, the RM is asked for confirmation.