Why Python needs fewer conferences

I’ve been to a lot of Python conferences over the years. I’ve stood in line for coffee with core developers, watched keynote speakers pitch their startups, and sat through talks that felt more like product demos than technical deep dives. And honestly, I think we’ve hit a point where the Python community needs fewer conferences—not more.

Here’s why.

First, there’s the session quality problem. When you have four or five big Python conferences each year, plus a dozen regional ones, the talk proposals start to look the same. “Ten things I learned refactoring a Flask app.” “How to deploy Django on Kubernetes.” “Async with asyncio for beginners.” I’ve seen these presentations recycled with minor tweaks at PyCon, EuroPython, PyData, and a half-dozen smaller events. The real value—the deep technical insights, the honest debugging stories, the uncomfortable trade-off decisions—gets diluted in the noise.

Second, conferences have become prohibitively expensive. A standard ticket to a major Python conference can cost $500-$1,500, not counting travel and accommodation. For many developers, especially those outside the US or Europe, that’s a month’s salary or more. The community talks a lot about inclusivity and diversity, but when the price of entry is that high, you’re effectively filtering out everyone who can’t afford it or whose employer won’t sponsor them. Free or low-cost online alternatives have tried to fill the gap, but they miss the human connection that makes conferences special.

Third, there’s the exhaustion factor. Ask any Python conference organizer or long-time attendee: the circuit has become a grind. People fly from one city to another, sit through back-to-back talks, network at evening socials, and return home with a bag of stickers and a lingering sense of burnout. The real learning happens in hallway conversations and late-night hack sessions, but those moments are increasingly rare when every conference tries to pack in sponsors, workshops, and keynotes.

Here’s a specific example from my experience. At a recent PyCon, I attended a talk on error handling in Python that was essentially a repackaged version of the official documentation. The speaker spent 20 minutes explaining try/except blocks, then rushed through the more interesting part—context managers and exception chaining—in the last five minutes. Meanwhile, in the hallway, a group of developers were discussing a real-world bug they’d found in a popular library’s exception handling. That conversation was worth more than the entire talk. But it happened by accident, not by design.

So what should we do instead?

Here are some ideas that actually work:

• Focus on a single, high-quality event per region. Instead of spreading attendance across four mediocre conferences, concentrate resources on one well-organized event with rigorous talk selection. The PyCon model is already close to this, but many regional conferences could benefit from merging or alternating years.

• Replace some conferences with smaller, themed workshops. A two-day workshop on Python performance optimization, with hands-on labs and limited attendance, often delivers more value than a four-day conference with 20 parallel tracks. The Python community already has great examples like the PyData workshops and the SciPy tutorials.

• Invest in virtual-first events with asynchronous elements. I know, we’re all tired of Zoom meetings. But a well-designed virtual conference with pre-recorded talks, live Q&A sessions, and persistent chat channels can actually increase participation from people who can’t travel. The key is to make it asynchronous enough that people in different time zones can engage on their own schedule.

• Encourage local meetups over global conferences. Sometimes the best Python discussion happens over pizza at a local user group. We should invest more in supporting these grassroots events rather than trying to scale up the conference model.

I’m not saying conferences are useless. They can be transformative—I’ve met collaborators, learned new libraries, and left feeling energized. But the Python community is mature enough to recognize that more isn’t always better. We need fewer, stronger conferences that prioritize depth over breadth, connection over consumption, and honest technical conversation over polished presentations.

Let’s stop chasing the conference expansion treadmill and focus on making the ones we have truly count.