➜

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.

作者 kristjan.jonsson
收信人 kristjan.jonsson, loewis, paul.moore, pitrou, python-dev, sbt, vstinner
日期 2012-06-19.15:06:24
SpamBayes Score -1.0
Marked as misclassified 是
Message-id <1340118385.29.0.434001096745.issue15038@psf.upfronthosting.co.za>
In-reply-to
内容
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.

None of the internal usages of condition variables makes this assumption about the order of wakeup from PyCOND_WAIT().
历史
日期 用户 动作 参数
2012-06-19 15:06:25kristjan.jonsson修改recipients: + kristjan.jonsson, loewis, paul.moore, pitrou, vstinner, python-dev, sbt
2012-06-19 15:06:25kristjan.jonsson修改messageid: <1340118385.29.0.434001096745.issue15038@psf.upfronthosting.co.za>
2012-06-19 15:06:24kristjan.jonsson链接issue15038 messages
2012-06-19 15:06:24kristjan.jonsson创建