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 Sebastian.Noack, asvetlov, christian.heimes, jyasskin, kristjan.jonsson, mklauber, pitrou, sbt
Date 2012-10-01.13:46:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349099144.3443.10.camel@localhost.localdomain>
In-reply-to <>
> A RW lock is part of POSIX threads [1]. It's usually a good idea to
> either use POSIX functions or to mimic their behavior. After all POSIX
> is an industry standard.

We've already departed from that. Our Lock is nothing like a mutex, for
example (it's more of a binary semaphore).
We follow POSIX when exposing POSIX APIs (as in the os module), but
otherwise we have our own abstractions, for example the 3.x I/O stack.
Date User Action Args
2012-10-01 13:46:54pitrousetrecipients: + pitrou, kristjan.jonsson, christian.heimes, jyasskin, asvetlov, sbt, mklauber, Sebastian.Noack
2012-10-01 13:46:54pitroulinkissue8800 messages
2012-10-01 13:46:54pitroucreate