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 hgibson50
Recipients Rhamphoryncus, giampaolo.rodola, gregory.p.smith, hgibson50, jcea, pitrou, sserrano, vstinner
Date 2008-10-09.05:39:08
SpamBayes Score 0.00733415
Marked as misclassified No
Message-id <>
> I doubt subclassability of RLock matters but who knows, people do code
> things.

I've recently done this to implement potential deadlock detection. I 
keep a record of the sequences of acquired locks, find unique 
sequences, then check for conflicts between each sequence. There's not 
much overhead and it highlighted some potential deadlocks where lock A 
and B were acquired AB in one route through code and BA in another 
route. The algorithm is a simplified version of that used in Linux - 

Date User Action Args
2008-10-09 05:39:11hgibson50setrecipients: + hgibson50, gregory.p.smith, jcea, Rhamphoryncus, pitrou, vstinner, giampaolo.rodola, sserrano
2008-10-09 05:39:11hgibson50setmessageid: <>
2008-10-09 05:39:10hgibson50linkissue3001 messages
2008-10-09 05:39:08hgibson50create