Merged
Conversation
Member
Author
|
PEP 809 can now shed the common parts and focus on what's different from PEP 803 (the new API and the versioning/support scheme). |
Member
|
I'll just withdraw it, probably with a comment to that effect, in case someone else decides to pick it up. I've got no bandwidth to push on it |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Discussions-TothreadPEP 123: Mark as Accepted)Statuschanged toAccepted/RejectedResolutionfield points directly to SC/PEP Delegate official acceptance/rejected post, including the date (e.g.`01-Jan-2000 <https://discuss.python.org/t/12345/100>`__)Discussions-To,Post-HistoryandPython-Versionup to date📚 Documentation preview 📚: https://pep-previews--4880.org.readthedocs.build/