➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sbt
Recipients kristjan.jonsson, loewis, paul.moore, pitrou, python-dev, sbt, vstinner
Date 2012-06-19.14:05:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340114704.54.0.944923215743.issue15038@psf.upfronthosting.co.za>
In-reply-to
Content 
> Let me elaborate: the GIL can perhaps suffer lost wakeups from time to 
> time. The Lock API certainly shouldn't.

I think with FORCE_SWITCHING defined (the default?) it is not possible for the thread releasing the GIL to immediately reacquire it (unless there is a spurious wakeup when waiting on switch_cond).

If all threads which wait on a condition are testing the same predicate then the stolen wakeup issue probably won't cause any misbehaviour.
History
Date User Action Args
2012-06-19 14:05:04sbtsetrecipients: + sbt, loewis, paul.moore, pitrou, kristjan.jonsson, vstinner, python-dev
2012-06-19 14:05:04sbtsetmessageid: <1340114704.54.0.944923215743.issue15038@psf.upfronthosting.co.za>
2012-06-19 14:05:03sbtlinkissue15038 messages
2012-06-19 14:05:03sbtcreate