News for hackers. Stuff that matters.
Re:Python's Hardest Problem (2012) by somejan on Tuesday June 04, 2013 @11:43AM (#5820102)
Having a look at the source, you get this for free in python. If you don't use any threads the overhead is just the checking of one (non-atomic) variable in the main eval loop, so that is at least as cheap as GOMAXPROCS=1 in Go. There is a small overhead of dropping/taking the gil around I/O functions, but it isn't worth optimizing the few nanoseconds that takes for the much slower i/o functions.

But if even this overhead is too much you can compile python without treading support.

Re:Python's Hardest Problem (2012) by somejan on Tuesday June 04, 2013 @02:17PM (#5821164)
Ok, the above is not really relevant, I misread the parent comment. Why the gil is not completely removed or made optional can be read at http://wiki.python.org/moin/GlobalInterpreterLock