Message 94135 - Python tracker

Message94135

Author	gregory.p.smith
Recipients	gregory.p.smith, pitrou
Date	2009-10-16.10:28:41
SpamBayes Score	0.00090583647
Marked as misclassified	No
Message-id	<1255688923.74.0.0855643142774.issue6721@psf.upfronthosting.co.za>
In-reply-to

Content
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.

Content

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.

History
Date	User	Action	Args
2009-10-16 10:28:43	gregory.p.smith	set	recipients: + gregory.p.smith, pitrou
2009-10-16 10:28:43	gregory.p.smith	set	messageid: <1255688923.74.0.0855643142774.issue6721@psf.upfronthosting.co.za>
2009-10-16 10:28:42	gregory.p.smith	link	issue6721 messages
2009-10-16 10:28:42	gregory.p.smith	create