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 Louis Brandy
Recipients Louis Brandy, Piotr Wysocki, cooperlees, drothera, gregory.p.smith, lukasz.langa, phantez, pixelbeat, vstinner
Date 2017-05-23.15:37:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks to everyone jumping in.

I need no convincing that mixing forks and threads isn't just a problem but a problem factory. Given that the rest of this code seems to try to avoid similar deadlocks with similar mutexes, I figured we'd want to include this mutex to make a best-effort at being safe here. That made it worth reporting. To be sure, I still believe that the application code that led us here needs deeper fixes to address the fork/thread problems.
Date User Action Args
2017-05-23 15:37:09Louis Brandysetrecipients: + Louis Brandy, gregory.p.smith, vstinner, pixelbeat, lukasz.langa, cooperlees, drothera, phantez, Piotr Wysocki
2017-05-23 15:37:09Louis Brandysetmessageid: <>
2017-05-23 15:37:09Louis Brandylinkissue30395 messages
2017-05-23 15:37:09Louis Brandycreate