Repository navigation
Conversation
| Python core developers. The Packaging Council is responsible for | ||
| establishing clear criteria for granting these rights, maintaining a record | ||
| of who has them, and for periodically reviewing the list. Python core |
There was a problem hiding this comment.
The PPC still needs to decide how exactly we'd do this. It looks like we'd need to do a PEP 1 update as well, so I'm inclined to put the listing there.
So... I've left the specifics slightly open-ended here since we probably don't wanna be updating the language here whenever the specifics change.
There was a problem hiding this comment.
@pradyunsg I believe submitting PR for a PEP 1 update to reflect the peps repo commit right and sponsorship of Packaging Council members themselves is separate from the broader to-be-decided criterion, and was already approved by the SC. It's basically a tweak to https://peps.python.org/pep-0001/#submitting-a-pep to add Packaging Council next to Typing Council, plus a fix to the first paragraph too probably (if you can be a Sponsor, you don't need a sponsor for your own PEPs).
If that sounds right, let's do a separate PR? I can do it if you want.
- Move delegation for Packaging PEPs to the PPC - Include virtual environments in the delegation - Allow the PPC to approve additional sponsors for packaging PEPs - Drop the explicit reference to the PyPA-based standards processes
2 participants
Following up from the PPC + SC meeting on 2026-10-08.