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 csernazs, jyasskin, kristjan.jonsson, neologix, pitrou, python-dev
Date 2012-04-11.11:40:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334144100.3328.11.camel@localhost.localdomain>
In-reply-to <>
Le mercredi 11 avril 2012 à 11:32 +0000, Charles-François Natali a
écrit :
> 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
> implementation).

That's right, but spurious wakeups would be a good argument against
accepting such an implementation. Or that implementation should be fixed
to avoid them.

That said, we couldn't use the POSIX implementation anyway, since our
API allows the user to choose the type of lock, while POSIX AFAICT would
only accept a POSIX mutex (which doesn't have the same semantics as an
arbitrary Python lock).
Date User Action Args
2012-04-11 11:40:33pitrousetrecipients: + pitrou, csernazs, kristjan.jonsson, jyasskin, neologix, python-dev
2012-04-11 11:40:33pitroulinkissue8799 messages
2012-04-11 11:40:33pitroucreate