➜

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 pitrou
Recipients kristjan.jonsson, loewis, paul.moore, pitrou, python-dev, sbt, vstinner
Date 2012-06-19.15:07:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340118266.3361.12.camel@localhost.localdomain>
In-reply-to <1340118385.29.0.434001096745.issue15038@psf.upfronthosting.co.za>
Content 
> The problem Richard describes isn´t a lost wakeup.  PyCOND_SIGNAL
> _will_ wake up _at least_ one thread.  It just isn't guaranteed to be
> one of those who previously called PyCOND_WAIT(): It could be a
> latecomer to the game, including the one who called Signal himself.
> If no such thread comes in to steal it, then one of the waiting
> threads _will_ wake up.

Ok, thanks for clearing up.
History
Date User Action Args
2012-06-19 15:07:47pitrousetrecipients: + pitrou, loewis, paul.moore, kristjan.jonsson, vstinner, python-dev, sbt
2012-06-19 15:07:47pitroulinkissue15038 messages
2012-06-19 15:07:46pitroucreate