3 ms·
What about all the scripts and programs that depend on the GIL to give correct results - often without even their authors knowing about it? I guess making this
by klibertp 4y ago
What about all the scripts and programs that depend on the GIL to give correct results - often without even their authors knowing about it? I guess making this opt-in with a compiler flag is ok, but I would be very, very careful about making it the default. If that ever happens, we will be one Python interpreter upgrade from Y2K-like disaster...
- danbala 4y agoalmost like people should test their code before using a new python version in production.
- klibertp 4y agoThat's the problem: the kind of issues the GIL prevents is notoriously hard to reproduce and debug. It would probably pass 90% of the test suites out there, unless you wrote yours with multi-threading in mind. Same for empirical tests by QA teams - they rarely cause enough load on the system for the bugs to surface. I might be too pessimistic here, but this really looks to me like a disaster waiting to happen...
- gcbirzan 4y agoBecause concurrency issues are notoriously easy to catch.
- alkonaut 4y agoTesting can’t prove the absence of bugs.
- js2 4y agoFUD. This effort is very carefully designed so that such programs continue to operate correctly. https://docs.google.com/document/d/18CXhDb1ygxg-YXNBJNzfzZsDFosB5e6BfnXLlejd9l0/edit https://docs.google.com/document/d/18CXhDb1ygxg-YXNBJNzfzZsD...