News for hackers. Stuff that matters.
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.

Re:Python 3 Q&A by a prolific core developer by slurgfest on Friday June 29, 2012 @06:41PM (#4179505)
The entire interpreter is written in C. Using facilities written in C, as documented, is not "subverting" anything. That's ridiculous hyperbole and it really doesn't help your credibility.
Re:Python 3 Q&A by a prolific core developer by Flimm on Friday June 29, 2012 @05:20PM (#4179150)
"unless the GIL is subverted via C extensions or similar."

I would hardly call I/O with Python built-in functions to be a subversion of the GIL.