➜

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 Lothsahn
Recipients Lothsahn, Mike.Meyer, alex, cvrebert, jcea, meador.inge, neologix, pitrou, rbcollins, vstinner
Date 2015-01-28.23:36:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1422488216.19.0.385576729722.issue13697@psf.upfronthosting.co.za>
In-reply-to
Content 
I am using Python 2.6.5 (we will be upgrading to Python 2.7.9 soon) and I recently ran into this bug.

If I do any locking in a signal handler with RLocks, the entire system can deadlock.  I'm using this to serialize my IO so we don't have mismatched lines in our logs.  It looks like RLock was implemented in C in 3.2.  While I don't care about the performance benefits of that rewrite, having a non-deadlocking RLock implementation would be nice.

Not sure if this issue can be fixed in 2.7, but it would be nice.

C RLock implementation here:
http://bugs.python.org/issue3001
History
Date User Action Args
2015-01-28 23:36:56Lothsahnsetrecipients: + Lothsahn, jcea, pitrou, vstinner, rbcollins, alex, cvrebert, meador.inge, neologix, Mike.Meyer
2015-01-28 23:36:56Lothsahnsetmessageid: <1422488216.19.0.385576729722.issue13697@psf.upfronthosting.co.za>
2015-01-28 23:36:56Lothsahnlinkissue13697 messages
2015-01-28 23:36:56Lothsahncreate