Re:Python 3 Q&A by a prolific core developer
by slurgfest on Friday June 29, 2012 @02:32PM
(#4178247)
It simply isn't true that "the GIL allows only one thread to run at a time."
"Note that potentially blocking or long-running operations, such as I/O, image processing, and NumPy number crunching, happen outside the GIL. Therefore it is only in multithreaded programs that spend a lot of time inside the GIL, interpreting CPython bytecode, that the GIL becomes a bottleneck."
The sky isn't falling, in the worst possible case you can still use Jython or whatever
Re:Python 3 Q&A by a prolific core developer
by dmbaggett on Friday June 29, 2012 @03:42PM
(#4178661)
Right, that's why I qualified my statement with ...unless the GIL is subverted via C extensions or similar.
The sky isn't falling, in the worst possible case you can still use Jython or whatever.
Sigh. I could port to C++ or whatever, too.
But it's still not the case that multiple threads "normally" run in parallel, with the OS ensuring fairness, which is what (I think) most programmers would expect threads to do in a general-purpose threaded language.