(Posted for the whole Steering Council.) As we’ve announced before, the Steering Council has decided to accept PEP 703 (Making the Global Interpreter Lock Optional in CPython) . We want to make it clear why, and under what expectations we’re doing so. It is clear to the Steering Council that theoretically, a no-GIL (or free-threaded) Python would be of great benefit, and the majority of the community seems in agreement. Threads have significant downsides and caveats, but they are widely adopte...
Earth-shattering news, but looks like it will take a s**t-ton of work before it becomes mainstream.
Yes, but it’s been under development for a while, they’re well aware of the complexity, and IIRC the work is being funded by Meta. So I think it will come sooner than one might expect.
Can’t wait. I’ve been squeezing every last inch of computing power out of Python for the last two years, leveraging asyncio and distributed architectures, and I think that it’s far from the slow tool that many people imagine. Now this.
I’ve been wishing to point out for a while (but I’m more of a lurker than a talker) that the real power of asyncio lies in well thought-out architectures based on cooperative multitasking: hard to fine tune, but impressively effective.