Skip to content

Conversation

@encukou
Copy link
Member

@encukou encukou commented Dec 12, 2024

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.)

Like in 3.11, this is not a security fix, but an internal feature meant to make backporting easier. Needs an exception from @pablogsal.

Tested on Sphinx 3.4 and 7.4 with a local change (as in GH-127827).
(On Sphinx 8.0 the build fails for unrelated reasons.)


Co-authored-by: Adam Turner 9087854+AA-Turner@users.noreply.github.com
Co-authored-by: Hugo van Kemenade 1324225+hugovk@users.noreply.github.com
(cherry picked from commit 7d24ea9)

gh-121277: Raise nice error on next as second argument to deprecated-removed (GH-124623)

(cherry-picked from e349f73)

Updates for 3.10

(cherry-picked from 3.11: f0895aa)

  • Use version, not arguments directly
…H-121278) 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 <9087854+AA-Turner@users.noreply.github.com> Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> (cherry picked from commit 7d24ea9) pythongh-121277: Raise nice error on `next` as second argument to deprecated-removed (pythonGH-124623) (cherry-picked from e349f73) Updates for 3.10 (cherry-picked from 3.11: f0895aa) * Use version, not arguments directly
@encukou encukou requested a review from pablogsal December 12, 2024 13:43
@pablogsal pablogsal merged commit 8773554 into python:3.10 Dec 13, 2024
15 checks passed
encukou added a commit to encukou/cpython that referenced this pull request Dec 20, 2024
…-121278) (pythonGH-127867) 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 <9087854+AA-Turner@users.noreply.github.com> Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> (cherry picked from commit 7d24ea9) pythongh-121277: Raise nice error on `next` as second argument to deprecated-removed (pythonGH-124623) (cherry-picked from e349f73) Updates for 3.9 (cherry-picked from 3.11: f0895aa) (cherry-picked from 3.10: 8773554) * Use version, not arguments directly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants