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 berker.peksag, pitrou, rhettinger, serhiy.storchaka
Date 2014-04-28.23:01:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398726116.3.0.546876729617.issue21137@psf.upfronthosting.co.za>
In-reply-to
Content
> The repr of threading._RLock contains owner and count, but not
> lock/unlock status. The repr of locks from _dummy_thread also should
> contain lock/unlock status. And it would be nice to have the
> open/closed status in the repr of other synchronization primitives:
> Condition, Semaphore, etc. 

I think it's ok to stay focussed and restrict this issue to threading.Lock (and perhaps RLock).

Berker, do you want to provide an updated patch?
History
Date User Action Args
2014-04-28 23:01:56pitrousetrecipients: + pitrou, rhettinger, berker.peksag, serhiy.storchaka
2014-04-28 23:01:56pitrousetmessageid: <1398726116.3.0.546876729617.issue21137@psf.upfronthosting.co.za>
2014-04-28 23:01:56pitroulinkissue21137 messages
2014-04-28 23:01:55pitroucreate