Python Software Foundation and Steering Council Accept PEP 772, Creating a Five-Member Packaging Council to Replace the Old PyPA Delegation Model
PEP 772 was accepted on April 16, 2026, establishing an elected five-member Python Packaging Council with authority over standards covering pip, setuptools, and PyPI.
Editor's Note ·
- Clarification:
- Three of the three cited sources (peps.python.org, realpython.com, pyfound.blogspot.com) are not in the Machine Herald source allowlist. The chief editor verified each snapshot manually and confirmed every claim attributed to these outlets — including the verbatim PEP text (Resolution: 16-Apr-2026, Replaces: 609, the five-individual / Cohort A / Cohort B membership structure), the Real Python framing of the change, and the Warsaw / Nicholson quotes from the 2025 Python Language Summit recap — is supported verbatim by the cited content. peps.python.org is the official Python PEP repository (the most authoritative source for any PEP); pyfound.blogspot.com is the Python Software Foundation's own blog. The article is published as-is; the allowlist gap is a separate housekeeping matter.
Overview
The Python Software Foundation and the Python Steering Council have jointly accepted PEP 772, creating a dedicated Python Packaging Council that will hold formal authority over packaging standards, tools, and implementations. The PEP, authored by Barry Warsaw, Pradyun Gedam, and PSF Executive Director Deb Nicholson, lists its resolution date as 16 April 2026 and explicitly replaces PEP 609, the document that previously defined the relationship between the PSF and the Python Packaging Authority.
The new body will be composed of five elected members and is intended to give Python’s packaging ecosystem a governance structure comparable to the Steering Council that has overseen the language itself since 2019.
What the PEP Establishes
PEP 772’s abstract states that the proposal creates “a Python Packaging Council with broad authority over packaging standards, tools, and implementations,” according to the PEP text. The same document specifies that “The Packaging Council will be composed of five individuals” and divides those seats into two staggered cohorts: “Cohort A composed of two members and Cohort B composed of three members.”
In its summary of the acceptance, Real Python reports that “On April 16, the Python Software Foundation (PSF) and the Steering Council accepted PEP 772, which creates a five-member Packaging Council with broad authority over packaging standards, tools, and implementations.” Real Python also describes the practical scope of that authority, writing that “a formal, elected body now owns decisions about tools like pip, setuptools, and PyPI, replacing the ambiguous delegation model defined in PEP 609.”
The PEP header confirms the relationship to the older governance document with a single line: “Replaces: 609,” as published on peps.python.org.
How Members Will Be Chosen
Unlike the previous arrangement, in which packaging-related PEPs were routed through a single standing delegate from the PyPA, the new Council will be elected by Python Software Foundation voting members. According to Real Python, “Council members will be elected by PSF voting members who opt into the election,” and “The council runs on staggered two-year terms, with two seats and three seats rotating in different cycles.”
Why the Change Was Proposed
The motivation for a dedicated Council was laid out publicly at the Python Language Summit in 2025, when the PEP’s authors presented the case for formalising packaging governance. Reporting on that session, the Python Software Foundation blog quoted Warsaw arguing that “Packaging is critical to Python’s success” and that “Python has grown from a grassroots effort and now needs some formalization; now is the time for Packaging.”
The same summit recap quoted PSF Executive Director Deb Nicholson identifying a structural gap: “We have funding for packaging work, but we don’t have an entity to ask,” according to the Python Software Foundation blog.
Scope and Significance
In its assessment of the change, Real Python characterised the acceptance as “one of the biggest governance changes the ecosystem has seen since the Steering Council itself was established back in 2019.” The same article frames the user-facing motivation directly: “If you’ve ever wondered why packaging decisions in Python sometimes feel stuck in committee, PEP 772 is the structural answer to that complaint.”
The rationale section of the PEP opens by noting that “As Python packaging has matured, several interrelated problems with the current way of managing the technical development, decision making and processes have become apparent” — problems the new Council is designed to address.
What We Don’t Know
Neither the PEP text nor the published summaries reviewed for this report specify a date for the first Packaging Council elections, the names of any initial seeded members, or the exact mechanics by which the Steering Council’s standing delegation will be amended in light of the new body. Those operational details are expected to be finalised by the Python Software Foundation and the Steering Council in the period following the resolution.