What is PEP 609?
PEP 609 establishes the governance model for the Python Packaging Authority (PyPA), the working group that maintains core Python packaging tools like pip, setuptools, and wheel.
What the PEP Defines
Before PEP 609, PyPA operated informally without a written governance structure. The PEP formalizes several key aspects:
- Membership: Anyone with commit access to a PyPA project is a member. New projects can join by requesting inclusion through the PyPA GitHub organization.
- Decision making: Decisions are made through informal consensus on discussion threads. If consensus cannot be reached, a formal vote among members can be called.
- Project lifecycle: PyPA projects are expected to follow Python packaging standards. Projects that become unmaintained can be archived or removed from the organization.
- Relationship to PEPs: PyPA members participate in the PEP process for packaging-related standards but do not have special authority over PEP acceptance — that remains with the Python Steering Council.
Why It Matters
PEP 609 provides transparency around how PyPA operates, making it clearer how packaging tools are maintained and how new tools can become part of the official ecosystem. This is particularly relevant given that many widely-used packaging tools like poetry and uv exist outside of PyPA.
Learn More
Last updated on