Skip to content
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

[3.13] gh-121277: Allow .. versionadded:: next in docs (GH-121278) #124718

Draft
wants to merge 2 commits into
base: 3.13
Choose a base branch
from

Conversation

encukou
Copy link
Member

@encukou encukou commented Sep 27, 2024

This backport includes a fix-up for a nicer error message (GH-124623)

draft for now: IMO it should go in 3.13.1. Let's first test it in an alpha release (3.14) rather than a final.

Issue: gh-121277


📚 Documentation preview 📚: https://cpython-previews--124718.org.readthedocs.build/

)

Make `versionchanged:: next`` expand to current (unreleased) version.

When a new CPython release is cut, the release manager will replace
all such occurences of "next" with the just-released version.
(See the issue for release-tools and devguide PRs.)

Co-authored-by: Adam Turner <[email protected]>
Co-authored-by: Hugo van Kemenade <[email protected]>
(cherry picked from commit 7d24ea9)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant