I think you underestimate the problems that will occur in a large code base when the GIL is gone. It'll play out like this: Test will be fine, but production w

I think you underestimate the problems that will occur in a large code base when the GIL is gone. It'll play out like this: Test will be fine, but production will have some weird bugs. Nobody understands it. The devs end up adding locks everywhere, bringing down performance, or creating dead locks. In the end, they migrate back to Python 3.16. Here's free lesson number 1: start adding stress tests now.