Skip to content

Update the Python Packaging delegations #368

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pradyunsg wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update the Python Packaging delegations #368

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 16 additions & 19 deletions process/standing-delegations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,30 +4,27 @@ This document serves as a public record of current standing delegations for
PEPs and other areas of authority, the reasons they were put in place, and
the circumstances under which they may no longer be needed.

## PyPA Delegations
## Packaging Council

Currently active packaging interoperability specifications are maintained in
the [PyPA Specifications] section in the Python Packaging User Guide and the
process for updating those specifications is documented in the [PyPA
Documentation].
The Packaging Council, set up in [PEP 772], oversees Python packaging
standards. Currently active packaging interoperability specifications are
maintained in the [Specifications] section of the Python Packaging User
Guide. The Steering Council delegates decisions on packaging PEPs, including
PEPs related to virtual environments, to the Packaging Council.

These delegations are expected to stand indefinitely. Any of the standing
delegates may also be a sponsor for any packaging-related PEP, regardless
of their Python core developer status.
The Packaging Council may also approve its members and other packaging
contributors as sponsors for packaging PEPs, without requiring them to be
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
Comment on lines +17 to +19

@pradyunsg pradyunsg Oct 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@rgommers rgommers Oct 18, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

developers may continue to sponsor packaging PEPs.

Standing PEP Delegations:

- Package Distribution Metadata PEPs: Paul Moore
- Package Index Interface PEPs: Donald Stufft

[PyPA Specifications]: https://packaging.python.org/specifications/
[PyPA Documentation]: https://www.pypa.io/en/latest/specifications/

As an exception to the process documented in PEP 1, these PEPs should
be announced/discussed in the [Packaging category] on Discourse,
instead of the PEPs category.
Packaging PEPs should be announced and discussed in the [Packaging category]
on Discourse instead of the PEPs category.

[Packaging category]: https://discuss.python.org/c/14
[PEP 772]: https://peps.python.org/pep-0772/
[Specifications]: https://packaging.python.org/specifications/

## Typing Council

Expand Down
Loading