➜

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, neologix, pitrou, sbt
Date 2012-10-04.01:02:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349312568.09.0.596815132763.issue8800@psf.upfronthosting.co.za>
In-reply-to
Content 
I don't like the API. Why should I write "rwlock.acquire_read()" instead of "rwlock.reader.acquire()"? There should be one obvious way to do it.

The fact that "reader_lock" and "writer_lock" return a new object every time is a bit suboptimal, IMO.

Also, RWLockBase should be private (_RWLockBase).

Ah, and the patch needs docs :)
History
Date User Action Args
2012-10-04 01:02:48pitrousetrecipients: + pitrou, kristjan.jonsson, christian.heimes, jyasskin, asvetlov, neologix, sbt, mklauber, Sebastian.Noack
2012-10-04 01:02:48pitrousetmessageid: <1349312568.09.0.596815132763.issue8800@psf.upfronthosting.co.za>
2012-10-04 01:02:48pitroulinkissue8800 messages
2012-10-04 01:02:47pitroucreate