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 JohanAR, davin, gvanrossum, itamarst, ncoghlan, pitrou, python-dev, rhettinger, sbt, serhiy.storchaka, tim.peters, yselivanov, zzzeek
Date 2017-08-19.12:05:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
Le 19/08/2017 à 12:09, Nick Coghlan a écrit :
> Would it be feasible to change the behaviour of non-reentrant locks such that:
> 1. They *do* keep track of the owning thread


> 2. Trying to acquire them again when the current thread already has them locked raises RuntimeError instead of deadlocking the way it does now?

No.  It's not a deadlock, since you can release a Lock from another thread.
Date User Action Args
2017-08-19 12:05:56pitrousetrecipients: + pitrou, gvanrossum, tim.peters, rhettinger, ncoghlan, zzzeek, python-dev, sbt, serhiy.storchaka, JohanAR, yselivanov, itamarst, davin
2017-08-19 12:05:56pitroulinkissue14976 messages
2017-08-19 12:05:56pitroucreate