PEP 684 was accepted – Per-interpreter GIL in Python 3.12

This is great and was a huge effort by Eric Snow and collaborators to make it happen.<p>To be clear, this is not &quot;PEP 703 – Making the Global Interpreter Lock Optional in CPython&quot;, by Sam Gross. PEP 703 is more ambitious and add quite a bit of complexity to the CPython implementation. PEP 684 mostly cleans things up and encapsulates global state better. The most distruptive change is to allow immortal objects. I hope PEP 703 can go in too, even with the downsides (complexity, bit slower single threaded performance).

So after this and some follow-on work, you can switch from multiprocess message passing parallelism to same-process message passing multi-interpreter parallelism? Which would decrease message passing overhead at cost of crash&#x2F;memory safety isolation.

This is really cool and I&#x27;m excited about learning this new concurrency model, which isn&#x27;t something I&#x27;ve ever said before or expected to say.<p>Most languages I used, python included, haven&#x27;t done concurrency in a way that added enough without taking so much away where I have been inclined to use it by default. Maybe this is a change from that for python.

Nudging closer to the Beam, eh?

Now we just need PEP 554 so this can actually be used from Python code.