[issue21913] Possible deadlock in threading.Condition.wait() in Python 2.7.7

Ned Deily added the comment: So do we agree that the resolution for this is "wont fix"? -- nosy: +ned.deily ___ Python tracker ___ ___

[issue21913] Possible deadlock in threading.Condition.wait() in Python 2.7.7

Antoine Pitrou added the comment: Josh, your analysis is right, I had forgotten that we had improved this point in 3.x (interruptibility of lock.acquire()). It is *extremely* unlikely to be backported to 2.7, though, since it is really an enhancement. -- __

[issue21913] Possible deadlock in threading.Condition.wait() in Python 2.7.7

Josh Rosenberg added the comment: Antoine: It's possible this is a legitimate failure in the signal handling code. The lack of a RuntimeError seems more likely to be due to the code never executing, not an issue with Condition.wait/Condition.notify. --

[issue21913] Possible deadlock in threading.Condition.wait() in Python 2.7.7

Antoine Pitrou added the comment: So the problem is mostly that 2.7 gives less diagnosis information than 3.x about an incorrect use of the API. I don't think that's very worthy of a bugfix, IMHO. Just use 3.x :-) -- nosy: +neologix ___ Python track

[issue21913] Possible deadlock in threading.Condition.wait() in Python 2.7.7

Sangeeth Saravanaraj added the comment: I am convinced that the code is wrong. It was written with wrong assumptions. But Python 2.7 behaves differently compare to Python 3.4. I am not expecting the same behavior in Python 2.7 as in Python 3.4 but I am expecting that some form of exception is

[issue21913] Possible deadlock in threading.Condition.wait() in Python 2.7.7

Josh Rosenberg added the comment: So you want it to raise the same exception that is raised in Python 3.4? Either way, I don't think this is a deadlock (to get a deadlock, you'd have to have contested locks; this lock is being acquired only once). You're explicitly violating the rules of using

[issue21913] Possible deadlock in threading.Condition.wait() in Python 2.7.7

New submission from Sangeeth Saravanaraj: Python version 2.7.7 Mac OS Darwin Kernel Version 13.2.0 I have the following code which when executed waits to be interrupted by SIGINT, SIGTERM or SIGQUIT. When an object is initialized, it creates a threading.Condition() and acquires() it! The progr