Reverting the incremental GC in Python 3.14 and 3.15
Summary
This article discusses the decision to revert the incremental garbage collection feature in Python 3.14 and 3.15.
Similar Articles
Python 3.14 garbage collection rigamarole
Python 3.14 introduced an incremental garbage collector that was later reverted in 3.14.5 due to memory pressure reports. This article explains the changes, their impact, and the controversy around the revert.
@DailyDoseOfDS_: Finally, Python 3.14 lets you disable GIL! It's a big deal because earlier, even if you wrote multi-threaded code, Pyth…
Python 3.14 introduces the ability to disable the Global Interpreter Lock (GIL), enabling true parallel execution of multi-threaded code, overcoming a long-standing limitation.
Python 3.15: features that didn't make the headlines
Python 3.15 introduces smaller but notable features including graceful TaskGroup cancellation and context manager improvements for decorators, alongside major features like lazy imports and the tachyon profiler.
Watching Go's new garbage collector move through the heap
Go 1.26 makes Green Tea the default garbage collector, improving cache-friendliness. This article visualizes heap allocation with Go and C#, and discusses challenges with non-moving collectors and sparse pages.
What garbage collection actually costs
A technical article explains the true performance costs of garbage collection, contrasting tracing GCs, reference counting, and compile-time memory management in languages like Go, Java, Rust, Swift, and Python.