A few minor clarifications about the new developer process #1539
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
JelleZijlstra
approved these changes
Apr 16, 2025
AA-Turner
reviewed
Apr 17, 2025
Comment on lines
+41
to
+42
| requesting that the council either accept or reject the proposed membership. Technically, the | ||
| council may only `veto a positive vote <https://peps.python.org/pep-0013/#membership>`_. |
There was a problem hiding this comment.
Perhaps "requesting that the council confirms that it does not `veto the proposed membership`_."?
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.
No issue opened, but this just clarifies a few points about the SC's and DiR's role in the new core dev approval process.
📚 Documentation preview 📚: https://cpython-devguide--1539.org.readthedocs.build/