Having said that, I welcome Google's unladen swallow and hope they succeed in removing the GIL.
Here are some of the reasons Python uses a GIL: http://www.grouplens.org/node/244#comment-2493
Pasted for convenience:
""" Python has a GIL as opposed to fine-grained locking for several reasons:
--- It is faster in the single-threaded case.
--- It is faster in the multi-threaded case for i/o bound programs.
--- It is faster in the multi-threaded case for cpu bound programs that do their compute-intensive work in C libraries.
--- It makes C extensions easier to write: there will be no switch of Python threads except where you allow it to happen (i.e. between the Py_BEGIN_ALLOW_THREADS and Py_END_ALLOW_THREADS macros).
--- It makes wrapping C libraries easier. You don't have to worry about thread-safety. If the library is not thread-safe, you simply keep the GIL locked while you call it. """
Not really. Stackless Python still has a GIL, and if you want to make use of multiple threads, the GIL will still bite you.
Stackless allows you to write coroutines and has lots of cool abilities, but avoiding the GIL is simply not one of them as far as making use of multiple cores.
25 processors buys you a lot of programming time.
Note that, if I correctly understood, python event engine Twisted uses a custom C-implemented event loop to avoid this.
[1] http://www.igvita.com/2008/11/13/concurrency-is-a-myth-in-ru...
[2] http://groups.google.com/group/comp.lang.ruby/msg/e809a7a720...
Wow, seems like MacRuby uses OS threads and completely abolished the GIL [3].
[3] http://www.infoq.com/news/2009/06/macruby-drops-gil-threadin...