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:05:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340118156.3361.10.camel@localhost.localdomain>
In-reply-to <1340117146.2.0.377246754759.issue15038@psf.upfronthosting.co.za>
Content
> The implementation for multiprocessing.Condition is virtually the same
> as Listing 3 which the author says he thinks is "formally correct" but
> with "a fundamental performance problem".

To me, it seems similar to the last listing (under "The Sequel—NT and
PThreads"): there's a separate semaphore per waiter, used to wake it up
when signal() or broadcast() is called.
History
Date User Action Args
2012-06-19 15:06:00pitrousetrecipients: + pitrou, loewis, paul.moore, kristjan.jonsson, vstinner, python-dev, sbt
2012-06-19 15:05:59pitroulinkissue15038 messages
2012-06-19 15:05:57pitroucreate