]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.12] gh-121277: Allow `.. versionadded:: next` in docs (GH-121278) (GH-125980)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Mon, 28 Oct 2024 13:30:29 +0000 (14:30 +0100)
committerGitHub <noreply@github.com>
Mon, 28 Oct 2024 13:30:29 +0000 (14:30 +0100)
commit1e01dcf429e498ef592b4152b9663fbf263ea54c
tree06f646807681771e43aa887bd534127c2f24123c
parent05214e66b0e8d8e6c9255058903c3bfd75849a42
[3.12] gh-121277: Allow `.. versionadded:: next` in docs (GH-121278) (GH-125980)

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

(cherry picked from commit 7d24ea9db3e8fdca52058629c9ba577aba3d8e5c)

Also backports a minor fix-up:
gh-121277: Raise nice error on `next` as second argument to deprecated-removed (GH-124623)

(cherry-picked from commit e349f73a5ad2856b0a7cbe4aef7cc081c7aed777)

Co-authored-by: Petr Viktorin <encukou@gmail.com>
Doc/tools/extensions/pyspecific.py
Misc/NEWS.d/next/Documentation/2024-07-19-12-22-48.gh-issue-121277.wF_zKd.rst [new file with mode: 0644]