PEP 649: Mark as Final #4414
Closed
PEP 649: Mark as Final #4414
Conversation
This file contains hidden or 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
Member
|
I wonder if we should add some sort of note pointing to PEP-749 |
Member
Author
|
On second thought, it might be good to wait until after 3.14.0 final is released? I'll put this as draft. |
Member
|
This has been addressed in 5a1fddd. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
PEP 123: Mark as Final)Statuschanged toFinal(andPython-Versionis correct)canonical-docdirective(or
canonical-pypa-specfor packaging PEPs,or
canonical-typing-specfor typing PEPs)649 is an odd one as "PEP matches the final implementation" requires also reading 749. Thoughts?
📚 Documentation preview 📚: https://pep-previews--4414.org.readthedocs.build/