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 csernazs, jyasskin, kristjan.jonsson, neologix, pitrou, python-dev
Date 2012-04-11.11:32:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <1334141668.3328.8.camel@localhost.localdomain>
> Disagreed. Unit tests should definitely protect against the introduction
> of bugs (willingly or not). And unpredictable behaviour is usually
> considered a bug.
> If you think the condition variable specification should be changed, you
> can always ask for approval on python-dev. But I don't even see the
> point: you are not demonstrating any *practical* advantage in doing so.

One can imagine, for example, that another implementation (or maybe
CPython in a later version) exposes native condition variables on
POSIX, instead of emulating them (e.g. what happended for TLS
In that case, we could get spurious wakeups, and code not designed to
cope with them would break.
Date User Action Args
2012-04-11 11:32:43neologixsetrecipients: + neologix, csernazs, pitrou, kristjan.jonsson, jyasskin, python-dev
2012-04-11 11:32:43neologixlinkissue8799 messages
2012-04-11 11:32:42neologixcreate