Kill GIL

[Paul Rubin]

Mike Meyer <mwm at mired.org> writes:
> > Threads are also good for handling blocking I/O.
> 
> Actually, this is one of the cases I was talking about. I find it
> saner to convert to non-blocking I/O and use select() for
> synchronization. That solves the problem, without introducing any of
> the headaches related to shared access and locking that come with
> threads.

It's just a different style with its own tricks and traps.  Threading
for blocking i/o is a well-accepted idiom and if Python supports
threads at all, people will want to use them that way.