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 davin, mickp, paul.moore, pitrou, steve.dower, tim.golden, zach.ware
Date 2017-07-20.14:05:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1500559530.45.0.450551777511.issue30975@psf.upfronthosting.co.za>
In-reply-to
Content
As a matter of fact, the bug is in Condition (which is used by Event.wait() but not by Event.is_set(), hence your workaround).  Here is a reproducer script.

This looks like a hard issue to solve.  There is no way to know whether a process that used to be waiting for a Condition was killed.
History
Date User Action Args
2017-07-20 14:05:30pitrousetrecipients: + pitrou, paul.moore, tim.golden, zach.ware, steve.dower, davin, mickp
2017-07-20 14:05:30pitrousetmessageid: <1500559530.45.0.450551777511.issue30975@psf.upfronthosting.co.za>
2017-07-20 14:05:30pitroulinkissue30975 messages
2017-07-20 14:05:30pitroucreate