Python’s Maintainer Exodus: What’s Really Happening and Why It Matters

If you’ve been following Python news recently, you’ve probably seen the headlines: “Python faces maintainer crisis,” “Core developers leaving in droves,” and “Is Python in trouble?” As someone who works with Python daily, I’ll be honest—these stories made me pause. But after digging into the details, the situation is more nuanced than the alarm bells suggest.

The Numbers Behind the Headlines

Let’s start with the facts. In the last year, Python has lost several long-time core maintainers. According to the Python Software Foundation’s own reports, the number of active core developers has dropped by roughly 15% since 2022. We’ve seen high-profile departures from people who’ve shaped the language for over a decade.

The triggers vary: burnout from unpaid work, frustration with the pace of change, and disagreements over the direction of certain proposals like PEP 703 (the no-GIL plan) and the ongoing C API cleanups. Some have left for personal reasons, others because they feel Python’s governance isn’t keeping up with its growth.

Why Maintainers Are Quitting

This isn’t a Python-specific problem—open source maintainer burnout is well-documented across many projects. But Python faces unique challenges because of its sheer size. With over 20 million users worldwide, even a small change requires careful review, testing, and documentation.

One former maintainer, speaking on condition of anonymity, told PythonSkillset: “It’s not that I stopped loving Python. I stopped loving the endless debates with people who never contribute code but have very strong opinions.” That’s a sentiment you hear often in the volunteer open source world.

The core issue: Python’s volunteer model hasn’t scaled with its success. The core team handles everything from CPython’s C code to documentation to security patches—all while most have day jobs.

What This Means for Developers

For most PythonSkillset readers, this doesn’t mean you need to panic. Python isn’t going anywhere. The language is used in everything from AI/ML pipelines to web apps to system administration. The PSF has a $10 million+ budget and is actively hiring for paid maintainer positions.

What does change is the pace of innovation. We might see fewer major releases per year. The PEP process may slow down. And importantly, you’ll see more emphasis on community contributions—because without them, nothing gets done.

How PythonSkillset Readers Can Help

You don’t need to be a C expert or a PEP author to contribute. Here are real ways to support Python’s long-term health:

• Documentation patches are always needed. Fix a typo in a docstring and you’ve literally helped every reader.
• Testing and bug reporting is the most underrated help. Reproduce issues, write clear reports.
• Sponsor a maintainer via GitHub Sponsors or the PSF. Even $5/month helps.
• Contribute to the packaging ecosystem—tools like pip, setuptools, and cibuildwheel need love too.

The Bottom Line

The “crisis” is real, but it’s a growing pain, not a death knell. Python remains one of the most robust, well-designed languages in use today. What’s changing is the model: from a small group of volunteers to a more sustainable, funded approach. That takes time—and patience.

If you’re a PythonSkillset regular, you’re already part of the solution by being informed and engaged. Keep coding, keep contributing, and keep supporting the people who keep this language running.

What’s your take on the maintainer situation? Have you ever contributed back to Python or its ecosystem? I’d love to hear your experiences in the discussion below.