GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — [3.13] gh-121277: Allow `.. versionadded:: next` in docs (GH-121278) by encukou · Pull Request #124718 · python/cpython

Conversation

@encukou

@encukou encukou commented Sep 27, 2024 •
edited by github-actions Bot
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member

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/

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
encukou and others added 2 commits September 27, 2024 15:50
@encukou @AA-Turner @hugovk
pythongh-121277: Allow .. versionadded:: next in docs (pythonGH-121278
c339d39 
)

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)
@encukou
pythongh-121277: Raise nice error on next as second argument to dep…
99cae0e 
…recated-removed (pythonGH-124623)

(cherry-picked from e349f73)
This was referenced Sep 27, 2024
gh-121277: Allow .. versionadded:: next in docs #121278
Merged
Allow .. versionadded:: next in docs #121277
Closed
@encukou
Merge branch '3.13' into backport-7d24ea9-3.13
66c2978
@encukou

encukou commented Oct 23, 2024

Copy link
Copy Markdown
Member Author

This works as intended in 3.14, let's get it in 3.13.1.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@encukou
encukou marked this pull request as ready for review October 23, 2024 07:59
@bedevere-app bedevere-app Bot added the awaiting core review label Oct 23, 2024
@encukou
encukou merged commit dba992b into python:3.13 Oct 25, 2024
@bedevere-app bedevere-app Bot removed the awaiting core review label Oct 25, 2024
@encukou
encukou deleted the backport-7d24ea9-3.13 branch October 25, 2024 13:34
@encukou encukou added the needs backport to 3.12 only security fixes label Oct 25, 2024
@miss-islington-app

miss-islington-app Bot commented Oct 25, 2024

Copy link
Copy Markdown

Thanks @encukou for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12.
🐍🍒⛏🤖
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Oct 25, 2024
@encukou @miss-islington
[3.13] pythongh-121277: Allow .. versionadded:: next in docs (pytho…
5e2b229 
…nGH-121278) (pythonGH-124718)

* pythongh-121277: Allow `.. versionadded:: next` in docs (pythonGH-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 <[email protected]>
Co-authored-by: Hugo van Kemenade <[email protected]>
(cherry picked from commit 7d24ea9)

* pythongh-121277: Raise nice error on `next` as second argument to deprecated-removed (pythonGH-124623)

(cherry-picked from e349f73)
(cherry picked from commit dba992b)

Co-authored-by: Petr Viktorin <[email protected]>
@bedevere-app

bedevere-app Bot commented Oct 25, 2024

Copy link
Copy Markdown

GH-125980 is a backport of this pull request to the 3.12 branch.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
@bedevere-app bedevere-app Bot removed the needs backport to 3.12 only security fixes label Oct 25, 2024
encukou added a commit to encukou/cpython that referenced this pull request Dec 11, 2024
@encukou
[3.11] pythongh-121277: Allow .. versionadded:: next in docs (pytho…
f456e6f 
…nGH-121278) (python#124718)

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)

pythongh-121277: Raise nice error on `next` as second argument to deprecated-removed (pythonGH-124623)

(cherry-picked from e349f73)
@bedevere-app

bedevere-app Bot commented Dec 11, 2024

Copy link
Copy Markdown

GH-127827 is a backport of this pull request to the 3.11 branch.
All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
pablogsal pushed a commit that referenced this pull request Dec 11, 2024
@encukou
[3.11] gh-121277: Allow .. versionadded:: next in docs (GH-121278) (#…
f0895aa 
…124718) (#127827)

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

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)

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

(cherry-picked from e349f73)

* Import VersionChange

sphinx.domains.changeset.VersionChange exists at least since Sphinx 2.1,
according to: https://www.sphinx-doc.org/en/master/extdev/deprecated.html

* Get config from env

* Use version, not arguments directly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

1 participant

@encukou
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.