➜

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 kristjan.jonsson
Recipients kristjan.jonsson, loewis, paul.moore, pitrou, vstinner
Date 2012-06-13.09:44:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1339580667.06.0.592392257123.issue15038@psf.upfronthosting.co.za>
In-reply-to
Content 
While I'm confident about the correctness of this implementation (it´s in production use right now) I´d like comments on the architecture.

- Are people comfortable with the notion of an include file with an inline implementation of portable condition variables like this?
- Martin voiced concerns over having a _future_ compatible implementation in there with Windows 7 support only.  I thought it cool to have around, since it strenghtens the "portability" design of the pattern.
- Names of types/apis.  Am I doing it right?
History
Date User Action Args
2012-06-13 09:44:27kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, paul.moore, pitrou, vstinner
2012-06-13 09:44:27kristjan.jonssonsetmessageid: <1339580667.06.0.592392257123.issue15038@psf.upfronthosting.co.za>
2012-06-13 09:44:26kristjan.jonssonlinkissue15038 messages
2012-06-13 09:44:25kristjan.jonssoncreate