An interview with Pablo Galindo, one of the five members of the Python Steering Council who vet all revisions and additions to the programming language
Context & Ripple Effects
Python's governance story runs through Guido van Rossum: he created the language and steered it for decades before coming out of retirement to join Microsoft's Developer Division, leaving day-to-day stewardship to the five-member Steering Council that Pablo Galindo sits on. This interview is a rare look inside that body, which vets every revision and addition to the language.
The stakes are unusually high because Python's audience keeps expanding — [[a:940448|Stack Overflow's survey of 90K+ developers found it the fastest-growing major programming language]] — so each council decision lands on one of the largest developer bases in the industry.
First-order effects
- Galindo and his four council colleagues are the effective gatekeepers for what enters Python, meaning their review process — not any single creator — now determines the language's direction for millions of developers.
- With van Rossum employed at Microsoft rather than leading the project, the council's deliberations carry the full weight of deciding which proposals advance.
Second-order effects
- The committee model contrasts with C++, where creator Bjarne Stroustrup remains personally involved decades on — a visible alternative path other founder-led languages will be measured against.
- As Python's growth attracts more corporate-backed contributors, employers of core developers such as Microsoft gain informal leverage over which changes get prioritized through the council.
Third-order effects
- If AI coding agents keep absorbing more of the writing work — Claude Code already writes most of its own code per its product lead — the character of proposals reaching human vetting bodies like the Steering Council may shift toward machine-assisted contributions, testing whether a five-person review process can scale to that input volume.
- Sustained growth plus committee governance points toward Python's evolution becoming institutionalized: slower, consensus-driven, and less dependent on any individual's taste.
The trend: Major programming languages are moving from creator-led stewardship toward small-committee governance just as AI tooling begins reshaping how code and change proposals get written.