Withdraw PEP 759 #4248
Merged
Withdraw PEP 759 #4248
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
Because of the chicken/egg problem between DPO and PRs, the Resolution link will be filled in after copyedit approval of this PR, and before landing.
emmatyping
approved these changes
Jan 31, 2025
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.
After discussion among the authors @emmatyping and myself, we have decided to withdraw PEP 759. This PR changes the
StatustoWithdrawn, include aPEP withdrawnsection for the withdrawal rationale, and and incompleteResolutionheader.I'm setting this PR to Draft to prevent merging until I have a chance to post on the DPO thread that the PEP is withdrawn. Then I'll update the
Resolutionheader with the link, and merge the PR. However, please do review for copyediting purposes. Thanks!📚 Documentation preview 📚: https://pep-previews--4248.org.readthedocs.build/