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 neologix
Recipients JBernardo, neologix, pitrou, rhettinger, sbt
Date 2013-08-05.05:33:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM3OG2u00oo590xr0xYVWMy3k+oyEU9G0wbszyfM=hq==w@mail.gmail.com>
In-reply-to <1375667289.1.0.153864522958.issue18078@psf.upfronthosting.co.za>
Content
> FWIW, I don't support adding this functionality.  I don't see precedents for
> Condition Variables behaving this way in other languages.  Also, I don't
> think it is worth the added complexity, learning curve, and maintenance
> burden.  Condition variables are used as primitive for other mutexes and I
> think we ought to keep them somewhat simple.
>
> If someone wants to notify a specific waiter, then they have other options
> such as using a separate condition variable that shares the same underlying
> lock (much as the code in the queue module does).  That approach is easy to
> reason about.

That's exactly what the point I was trying to make, but Raymond sums
it really nicely :-)
History
Date User Action Args
2013-08-05 05:33:19neologixsetrecipients: + neologix, rhettinger, pitrou, sbt, JBernardo
2013-08-05 05:33:19neologixlinkissue18078 messages
2013-08-05 05:33:19neologixcreate