What is PEP 772?
PEP 772 creates the Python Packaging Council, a five-member elected body with authority over packaging standards, the Python Packaging User Guide, and ecosystem-wide packaging decisions. Accepted in April 2026, it replaces PEP 609’s informal governance model for the Python Packaging Authority (PyPA).
What problem it solves
Python’s packaging ecosystem has long been governed by a patchwork of groups with overlapping responsibilities. PyPA evolved organically without elections or regular coordination processes. Packaging-related PEPs relied on standing delegations from the Python Steering Council to individuals, creating bottlenecks when those individuals were unavailable. The Steering Council itself acknowledged that language governance and packaging governance require different expertise and different constituencies.
PEP 772 addresses this by creating a dedicated elected body focused solely on packaging.
How the council works
The council has five members organized in two staggered cohorts, each serving two-year terms. Elections follow the same process as PSF Board elections: any PSF voting member can become an elector, and any PSF voting member can be nominated. To prevent organizational capture, no more than two council members can share the same employer.
The council’s authority covers packaging interoperability standards (the PEPs that tools like uv, pip, and Poetry implement), the Packaging User Guide, and binding decisions about packaging tools and ecosystem changes. It prioritizes consensus over voting, but when votes happen, a simple majority of at least three non-abstaining members is required.
If the council cannot resolve a matter, it can refer the question to the Steering Council for a binding decision. Electors can remove individual members or dissolve the entire council through a two-thirds vote of no confidence.
What changes for Python developers
For most developers, nothing changes day-to-day. The tools work the same way. What changes is how packaging standards get made: instead of depending on individual volunteers’ availability and informal consensus, there is now a formal body accountable to the community through elections. Standards like PEP 751 (the lockfile format) and future packaging PEPs will go through this council rather than ad-hoc delegations.
This is part of a broader shift in Python packaging governance, addressing the fragmentation described in Why doesn’t Python just fix packaging?. The Packaging Council doesn’t unify all packaging under one roof, but it gives the standards process a permanent, elected home for the first time.