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 melwitt
Recipients gregory.p.smith, melwitt, vinay.sajip, vstinner
Date 2020-04-07.22:13:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Hi, I've been following the work related to:

because I encountered a problem where a standard library lock was held by a parent process at the time that child processes were forked, so the child processes got stuck behind the inherited held locks.

But, if I'm understanding correctly, this issue is fixing something in python logging specifically and not all standard library locks in general.

My question is, will there be a way to reinit standard library locks in general using _at_fork_reinit()? That is, should we expect a future fix in python to do this or is the recommendation to continue to ensure the application reinits locks during process start if we know the process could be a child?

Thanks for your advice.
Date User Action Args
2020-04-07 22:13:17melwittsetrecipients: + melwitt, gregory.p.smith, vinay.sajip, vstinner
2020-04-07 22:13:17melwittsetmessageid: <>
2020-04-07 22:13:17melwittlinkissue40091 messages
2020-04-07 22:13:16melwittcreate