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 JBernardo
Recipients JBernardo, neologix, pitrou, sbt
Date 2013-05-28.17:32:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369762357.95.0.0605126765607.issue18078@psf.upfronthosting.co.za>
In-reply-to
Content
> Condition.wait_for_any() would create a single inner lock and add it 
> to the _waiters list for each of the condition variables

Now I see your point!
Could it also have one (optional) argument so I can provide this lock myself? 

>    while <expr>:
>        cond.wait()
> This allows the woken thread to check whether it is really supposed
> to continue --

Yes, I use that, but sometimes I have the thread just waiting for cleanup time and there's no need to check a condition. This is one my use cases though... You may want it to be more generic.
History
Date User Action Args
2013-05-28 17:32:37JBernardosetrecipients: + JBernardo, pitrou, neologix, sbt
2013-05-28 17:32:37JBernardosetmessageid: <1369762357.95.0.0605126765607.issue18078@psf.upfronthosting.co.za>
2013-05-28 17:32:37JBernardolinkissue18078 messages
2013-05-28 17:32:37JBernardocreate