Python Packaging Council Holds Its Inaugural Election as 17 Candidates Vie for Five Seats
The Python Software Foundation announced 17 candidates for the first Python Packaging Council election on August 13, with voting scheduled for September 1-15.
Editor's Note ·
- Correction:
- The article quotes LWN as saying the council "received approval from the Python steering council in April." LWN's actual sentence reads: "the Python packaging council that was approved by the Python steering council in April." The underlying fact (steering council approval in April) is accurate; the wording was paraphrased rather than quoted verbatim.
- Correction:
- The article quotes LWN as saying: "Members eligible to vote through the PSF must confirm their participation by August 25. The voting period runs from September 1 through September 15." LWN's actual sentences read: "PSF voting-eligible members must affirm their intention to vote in this election by August 25. Voting begins on September 1, and ends on September 15." The dates and mechanics are accurate; the wording was paraphrased rather than quoted verbatim.
Overview
The Python Software Foundation announced the candidate list for the first election to the Python Packaging Council on August 13, opening the process that will seat the five-member body created earlier this year to govern packaging standards, tools, and implementations across the Python ecosystem. According to the Python Software Foundation blog, “This election has 17 nominees for 5 open seats on the council.”
The council itself was established by PEP 772, which the PSF and the Python Steering Council previously accepted on April 16, 2026, replacing the prior arrangement in which a single standing delegate from the Python Packaging Authority handled packaging-related decisions. LWN reports that the council “received approval from the Python steering council in April.”
What We Know
The election fills all five seats on the Packaging Council at once, since this is the body’s inaugural vote. Seats are split into two cohorts with different term lengths. Per the PSF announcement, “The two candidates receiving the highest number of votes shall be designated Cohort A with a two year term, and the three candidates receiving the next highest number of votes shall be designated Cohort B with a one year term.”
After this first election, the staggered structure becomes the norm. The same PSF post states that “In future elections, each cohort will be elected for a full two-year term in alternating years, so that roughly half of the PPC turns over each cycle.”
The election follows a fixed timeline published by the PSF:
- Nominations opened Tuesday, July 28, at 2:00 pm UTC
- Nominations closed Tuesday, August 11, at 2:00 pm UTC
- Candidates were announced Thursday, August 13
- Voters must affirm their intent to participate by Tuesday, August 25, at 2:00 pm UTC
- Voting runs from Tuesday, September 1, at 2:00 pm UTC through Tuesday, September 15, at 2:00 pm UTC
LWN summarizes the mechanics for eligible participants: “Members eligible to vote through the PSF must confirm their participation by August 25. The voting period runs from September 1 through September 15.”
The official nominees page on python.org lists all 17 candidates: Jonathan Dekhtiar, Donald Stufft, Axel Obermeier, Bernat Gabor, Cary Hawkins, Matthias Köppe, Paul Moore, Dan Yeaw, Saurav Singla, Brett Cannon, Eli Schwartz, William Woodruff, Pradyun Gedam, Ralf Gommers, Lucas Colley, Timothy Hopper, and Henry Schreiner.
The announcement itself was posted by Pradyun Gedam, one of the co-authors of PEP 772, who also opened the central discussion thread on the Python Discourse forum tracking election-related announcements.
What We Don’t Know
The sources reviewed for this report do not disclose interim vote counts, the identities of PSF members who have affirmed their intent to vote, or which candidates will ultimately land in Cohort A versus Cohort B. Those outcomes will not be known until after the September 15 voting deadline and the subsequent count.
Why It Matters
As previously reported, the Packaging Council was designed to give tools like pip, setuptools, and PyPI a formal, elected governance body in place of the informal delegation model that preceded it. This election is the first practical test of that structure: the outcome will determine who holds authority over packaging standards and tooling decisions that affect the broader Python developer and package-management ecosystem for the next one to two years.