Python 3.14 and 3.15 Revert Incremental GC: When the Garbage Collector Collects Your Sanity

Big changes are brewing in Python land, and no, it's not yet another async framework. The CPython team has made a bold call: revert the incremental garbage collector (GC) in versions 3.14 and 3.15.

If you've ever tried to deploy on a Friday evening and hit a segmentation fault, you'll get it. The incremental GC, which was supposed to speed up garbage collection, turned out to be one of those "improvements" that breaks everything. Like assembling IKEA furniture without instructions: the parts look nice, but the chair wobbles.

What went wrong?

According to the developers, the incremental GC in Python 3.14 and 3.15 caused instability and performance regressions, especially in multithreaded applications. Instead of trying to fix it, they decided to roll back to the good old generational GC. Sure, they could have left it and hoped for the best, but that's not Python's style — stability is key, even if it's boring.

Developers who already got used to the new GC will likely recall the old pain: "Why is everything crashing in production?" The answer is simple: because the garbage collector decided to collect not just objects, but your sanity as well.

What does this mean for you?

If you're using Python 3.14 or 3.15, get ready for changes. The GC revert could affect application performance, especially memory-heavy ones. But don't panic: the devs promise the new GC will return when it's ready, and until then — back to basics.

Commentary by METABYTE studio: This GC revert reminds us that in IT, sometimes better is the enemy of good. If your project needs stability over experiments, we can help you set up an environment where the garbage collector doesn't collect your bugs.