Kill GIL

[Aahz]

In article <86sm405d38.fsf at guru.mired.org>, Mike Meyer  <mwm at mired.org> wrote:
>aahz at pythoncraft.com (Aahz) writes:
>> In article <868y5t6sal.fsf at guru.mired.org>, Mike Meyer  <mwm at mired.org> wrote:
>>>
>>>Here here. I find that threading typically introduces worse problems
>>>than it purports to solve.
>>
>> 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 may be saner, but Windows doesn't support select() for file I/O, and
Python's threading mechanisms make this very easy.  If one's careful
with application design, there should be no locking problems.  (Have you
actually written any threaded applications in Python?)
-- 
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

"The joy of coding Python should be in seeing short, concise, readable
classes that express a lot of action in a small amount of clear code -- 
not in reams of trivial code that bores the reader to death."  --GvR