Nikolaj Baer wrote:
.. and on my core duo laptop, threading in python immediately hops onto the second core, which is very useful when i am writing a quick script to do some intensive task once (as opposed to writing a c
I'm confused. How do you reconcile all of this with the fact that python has a Global Interpreter Lock which prevents any two parts of the interpreter from ever running at the same time? This prevents python from ever being able to take advantage of more than one cpu core at a time. Andrew makes some very good points about our current languages being dead if they do not support real concurrency and support it well.
-- Tracy R Reed http://ultraviolet.org A: Because we read from top to bottom, left to right Q: Why should I start my reply below the quoted text -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
