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 rnk
Recipients gregory.p.smith, hobb0001, jyasskin, pitrou, rnk
Date 2010-07-10.17:28:14
SpamBayes Score 0.021455435
Marked as misclassified No
Message-id <1278782899.83.0.425974392712.issue8844@psf.upfronthosting.co.za>
In-reply-to
Content
Here is a new version of a patch that updates recursive locks to have the same behavior.  The pure Python RLock implementaiton should be interruptible by virtue of the base lock acquire primitive being interruptible.

I've also updated the relevant documentation I could find.  I've surely missed some, though.

I also got rid of the _intr version of lock acquisition and simply added a new parameter to the _timed variant.  The only two callers of it are the ones I updated in the _thread module.
History
Date User Action Args
2010-07-10 17:28:19rnksetrecipients: + rnk, gregory.p.smith, pitrou, jyasskin, hobb0001
2010-07-10 17:28:19rnksetmessageid: <1278782899.83.0.425974392712.issue8844@psf.upfronthosting.co.za>
2010-07-10 17:28:17rnklinkissue8844 messages
2010-07-10 17:28:16rnkcreate