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 Sebastian.Noack, asvetlov, christian.heimes, jyasskin, kristjan.jonsson, mklauber, neologix, pitrou, sbt
Date 2012-10-02.10:59:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The unlock operation is the same, so now you have to arbitrarily pick one 
> of the "lockd" and chose release().

That depends on the implementation.  In the three implementations on

the unlock operateration is different for readers and writers.

> Why take a construct which is essentially a lock that can be acquired in two 
> different ways and force people to view it as separate objects?

I don't see why writing


really requires a different way of thinking compared to writing



Date User Action Args
2012-10-02 10:59:55sbtsetrecipients: + sbt, pitrou, kristjan.jonsson, christian.heimes, jyasskin, asvetlov, neologix, mklauber, Sebastian.Noack
2012-10-02 10:59:55sbtsetmessageid: <>
2012-10-02 10:59:55sbtlinkissue8800 messages
2012-10-02 10:59:55sbtcreate