➜

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, jyasskin, kristjan.jonsson, mklauber, pitrou, sbt
Date 2012-09-30.20:10:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349035850.1.0.773756049578.issue8800@psf.upfronthosting.co.za>
In-reply-to
Content 
Ok, since we're bikeshedding, I like Richard's proposal best:

> Personally, I would prefer to make the shared and exclusive locks
> attributes of the same object, so one could do
> 
>    with selock.shared:
>       ...
> 
>    with selock.exclusive:
>       ...

Please note, the "same object" could simply be a namedtuple instance.

Also I think "shared/exclusive" indeed conveys the semantics better than "read/write".
History
Date User Action Args
2012-09-30 20:10:50pitrousetrecipients: + pitrou, kristjan.jonsson, jyasskin, asvetlov, sbt, mklauber, Sebastian.Noack
2012-09-30 20:10:50pitrousetmessageid: <1349035850.1.0.773756049578.issue8800@psf.upfronthosting.co.za>
2012-09-30 20:10:50pitroulinkissue8800 messages
2012-09-30 20:10:49pitroucreate