global interpreter lock not working as it should

[anton wilson]

> If you try the current CVS version of Python, the implementation of "the
> lock" on Linux has changed to use POSIX semaphores instead.  They may or
> may not act more like you hope -- I don't know (haven't tried it).  It
> seems possible that they might, since semaphores came out of the POSIX
> realtime extensions, where people feel much freer to make unreasonable
> <wink> demands.

My unreasonable demands have been met by the CVS version! :D Thanks

>
> > ...
> > I have a feeling that there is a hidden race condition between when the
> > thread wakes up the other thread and tries to reaquire the lock.
>
> "The race" would be in the platform implementation of
> pthread_cond_signal(), but I expect that's working the way its author
> intended.