"Python 3.14 shipped with a new incremental garbage collector. However, we’ve had a number of reports of significant memory pressure in production environments.
We’ve decided to revert it in both 3.14 and 3.15, and go back to the generational GC from 3.13."
Sounds the right move for me
NooneAtAll3•32m ago
I'm genuinely surprised that python change was even possible without PEP
Fizzadar•30m ago
Exactly! Would like to understand more how that came about. The PEP exists for a reason.
AdamN•25m ago
Yeah it seems like a miss. I guess the thinking was that it wasn't developer-facing and just an internal optimization. But of course any change to garbage collection will change the memory and cpu dynamics of the process in a material way.
askllk•25m ago
All these issues were known in previous attempts for removing the GIL. But if Instagram/Meta want it, everyone stands to attention and finds out the obvious problems years later. Kind of like in geopolitics.
I hope Meta switches Instagram to PHP/Hack so they leave Python alone.
simonw•16m ago
The no-GIL work (free-threading) is unrelated to this incremental GC work.
davidkwast•41m ago
We’ve decided to revert it in both 3.14 and 3.15, and go back to the generational GC from 3.13."
Sounds the right move for me