PEP 630: Isolating Extension Modules#1574
Merged
Merged
PEP 630: Isolating Extension Modules#1574
Conversation
Member
|
Other than CI failing it's fine by me, although if you're going to put it out with There's currently no reserved numbers, so feel free to grab the next number. |
Member
|
CI failure is like #1571 (comment), fix is to install pygments. |
isidentical
reviewed
Aug 26, 2020
Member
Author
|
Thank you, Brett! |
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
5 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.
See the capi-sig discussion.
@python/pep-editors, I'd appreciate your opinion on this “current state+HOWTO” Informational PEP.
PEP 1 seems written with Standards Track PEPs in mind, so I skipped on some advice from it.
On the
XXXnotes: I'd like to fix those after this becomes a PEP, so I can more easily refer to this document in discussions about a good place for the file.