3 ms·
It seems like every 5 years I hear about how someone is going to make python not have a GIL, improve performance drastically, etc etc. Then reality comes in an
by bfrog 3y ago
It seems like every 5 years I hear about how someone is going to make python not have a GIL, improve performance drastically, etc etc.
Then reality comes in and says, "nah".
Honestly at some point its better to likely start porting code to a language where you can control parallelism better. There's a few nice modern options that don't involve all the headaches of C++ or C. Could even be extensions as has been the case since the dawn of time.
- voz_ 3y agoBad faith take.
- kmod 3y agoIgnoring the pessimism for a moment But this nogil version is the first time we have an actually working GIL removal. All of the other ones were incomplete to the point of being non starters, and mostly served as discussion material. This is an actually working implementation which deals with the subtle issues that the other projects didn't even get to, and has gotten to the point that it's a technical possibility to commit it to main (though obviously with a huge migration to think about). So in this sense this is a very different discussion than all of the previous discussions about the GIL
- notatallshaw 3y agoThe difference between this attempt and previous attempts is: * The PEP has been announced to be accepted (Steering Council are still working on details for final wording) * Many things are already landing on CPython main in preparation for this Unless something absolutely show stopping comes up in the next 12 months it will almost certainly released in 3.13 or 3.14 as an optional compiler flag.