Fix nesting of 'Pending Removal in Python 3.14' #101637
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc @hugovk as an author of the section. |
hugovk
approved these changes
Feb 7, 2023
There was a problem hiding this comment.
Thanks!
I think what happened: "Pending Removal in Python 3.13" and "Pending Removal in Future Versions" were added first, at the "==" level.
Then concurrently PRs were opened to add "Pending Removal in Python 3.14" at "==" (#94546), and also switch the existing ones from "==" to "=" (#94762), so they just went out of sync :)
|
Doctest failure is unrelated and has already been fixed in #101642. |
hugovk
changed the title
Pending Removal in Python 3.14
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In What’s New In Python 3.12, subsections of Pending Removal in Python [...] must be children of Deprecated.
However, [...] 3.13 breaks this being a sibling instead and making the following [...] Future Versions its own child: