Python threads: backed by OS threads?

[Courageous]

> Unfortunately, the locking mechanism is very simple: it doesn't know
> whether you're going to run into trouble or not, so it always acquires
> the lock so that only one thread of Python code can run at any time.
> 
> However, I/O operations can effectively multithread, so if you're doing
> a lot of I/O, you may see a performance improvement.  One of my programs
> ran up to 80% faster when moved from a single-processor to a
> dual-processor machine.

I see. Well, then all things considered, I have no idea why one
would want to use python/OS threads at all. The uthread implementation
on stackless really rips.



C/