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 itamarst
Recipients JohanAR, itamarst, sbt
Date 2014-02-17.18:50:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This is not specifically a signal issue; it can happen with garbage collection as well if you have a Queue.put that runs in __del__ or a weakref callback function.

This can happen in real code. In my case, a thread that reads log messages from a Queue and writes them to disk. The thread putting log messages into the Queue can deadlock if GC happens to cause a log message to be written right after Queue.put() acquired the lock.
Date User Action Args
2014-02-17 18:50:43itamarstsetrecipients: + itamarst, sbt, JohanAR
2014-02-17 18:50:43itamarstsetmessageid: <>
2014-02-17 18:50:43itamarstlinkissue14976 messages
2014-02-17 18:50:43itamarstcreate