summaryrefslogtreecommitdiffstats
path: root/Python/Python-ast.c
diff options
context:
space:
mode:
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2024-10-28 13:30:29 (GMT)
committerGitHub <noreply@github.com>2024-10-28 13:30:29 (GMT)
commit1e01dcf429e498ef592b4152b9663fbf263ea54c (patch)
tree06f646807681771e43aa887bd534127c2f24123c /Python/Python-ast.c
parent05214e66b0e8d8e6c9255058903c3bfd75849a42 (diff)
downloadcpython-1e01dcf429e498ef592b4152b9663fbf263ea54c.zip
cpython-1e01dcf429e498ef592b4152b9663fbf263ea54c.tar.gz
cpython-1e01dcf429e498ef592b4152b9663fbf263ea54c.tar.bz2
[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>
Diffstat (limited to 'Python/Python-ast.c')
0 files changed, 0 insertions, 0 deletions