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 gregory.p.smith
Recipients gregory.p.smith, pitrou
Date 2009-10-16.10:28:41
SpamBayes Score 0.000905836
Marked as misclassified No
Message-id <>
no need for that.  the problem is that they're held by a thread that
does not exist in the newly forked child process so they will never be
released in the new process.

example: if you fork while another thread is in the middle of logging
something and then try to log something yourself in the child, your
child process will deadlock on the logging module's lock.

locks are not shared between processes so reinitializing them with a new
object wouldn't do anything.
Date User Action Args
2009-10-16 10:28:43gregory.p.smithsetrecipients: + gregory.p.smith, pitrou
2009-10-16 10:28:43gregory.p.smithsetmessageid: <>
2009-10-16 10:28:42gregory.p.smithlinkissue6721 messages
2009-10-16 10:28:42gregory.p.smithcreate