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 sbt
Recipients kristjan.jonsson, loewis, paul.moore, pitrou, python-dev, sbt, vstinner
Date 2012-06-19.18:08:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340129334.79.0.81958754259.issue15038@psf.upfronthosting.co.za>
In-reply-to
Content
1.41     Generic emulations of the pthread_cond_* API using
    1.42     earlier Win32 functions can be found on the Web.
    1.43     The following read can be edificating (or not):
    1.44     http://www.cse.wustl.edu/~schmidt/win32-cv-1.html
    1.45 +
    1.46 +   See also 
    1.47  */

1.45 and 1.46 should be removed?

Also I would not recommend the win32-cv-1.html page as "edificating" (edifying?).  The implementations all either suffer from the same stolen wakeup issue or are broken.*


* win32-cv-1.html assumes that SignalObjectAndWait() is atomic and that PulseEvent() is guaranteed to wake a waiting thread if there is one -- but Microsoft's documentation now admits that both these assumptions are false.
History
Date User Action Args
2012-06-19 18:08:55sbtsetrecipients: + sbt, loewis, paul.moore, pitrou, kristjan.jonsson, vstinner, python-dev
2012-06-19 18:08:54sbtsetmessageid: <1340129334.79.0.81958754259.issue15038@psf.upfronthosting.co.za>
2012-06-19 18:08:54sbtlinkissue15038 messages
2012-06-19 18:08:53sbtcreate