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 neologix
Recipients ionelmc, neologix, nirs, serhiy.storchaka
Date 2014-11-02.15:44:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414943059.82.0.929824760315.issue22697@psf.upfronthosting.co.za>
In-reply-to
Content
> Maries Ionel Cristian added the comment:
>
> Serhiy, I don't think this is a duplicate. Odd that you closed this without any explanation.
>
> This happens in a internal lock in cpython's runtime, while the other bug is about locks used in the logging module (which are very different).

Yes, this is a duplicate. Whether the lock is an internal or a user-created one doesn't change anything, it's always the same problem of having a lock locked by another thread at the time of the fork().
History
Date User Action Args
2014-11-02 15:44:19neologixsetrecipients: + neologix, nirs, ionelmc, serhiy.storchaka
2014-11-02 15:44:19neologixsetmessageid: <1414943059.82.0.929824760315.issue22697@psf.upfronthosting.co.za>
2014-11-02 15:44:19neologixlinkissue22697 messages
2014-11-02 15:44:19neologixcreate