Reverting the incremental GC in Python 3.14 and 3.15
discuss.python.org
Reverting the incremental GC in Python 3.14 and 3.15
1–10 of 134 posts
Re: Reverting the incremental GC in Python 3.14 and 3.15
#2"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
Re: Reverting the incremental GC in Python 3.14 and 3.15
#3I'm genuinely surprised that python change was even possible without PEP
Re: Reverting the incremental GC in Python 3.14 and 3.15
#4I'm genuinely surprised that python change was even possible without PEP
Exactly! Would like to understand more how that came about. PEP exists for a reason.
Re: Reverting the incremental GC in Python 3.14 and 3.15
#5All 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.
Re: Reverting the incremental GC in Python 3.14 and 3.15
#6I'm genuinely surprised that python change was even possible without PEP
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.
Re: Reverting the incremental GC in Python 3.14 and 3.15
#7All 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.
The no-GIL work (free-threading) is unrelated to this incremental GC work.
Free-threading actually uses its own, separate GC: https://labs.quansight.org/blog/free-threaded-gc-3-14
Re: Reverting the incremental GC in Python 3.14 and 3.15
#8I'm genuinely surprised that python change was even possible without PEP
Makes ya miss having a BDFL. Dang I didn't realize he's 70 now.
Re: Reverting the incremental GC in Python 3.14 and 3.15
#9In the world of AI written code, Python just doesn’t make sense. Converted about 100k lines in the last few months to golang and the performance is life changing. Curious if we will see global Python adoption fall by 75% or more in the next few years.
Re: Reverting the incremental GC in Python 3.14 and 3.15
#10In the world of AI written code, Python just doesn’t make sense. Converted about 100k lines in the last few months to golang and the performance is life changing. Curious if we will see global Python adoption fall by 75% or more in the next few years.
nothing about the performance characteristics of python changed with AI so why would you use python over golang if performance is a requirement/bottleneck? Trying to understand the reasoning as to me golang and python are equally simple to write and understand.