Message 244116 - Python tracker

➜

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	yselivanov
Recipients	christian.heimes, gvanrossum, martius, neologix, vstinner, yselivanov
Date	2015-05-26.17:51:24
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1432662684.39.0.34715023867.issue21998@psf.upfronthosting.co.za>
In-reply-to

Content
> I was thinking only in the child. The parent should be able to continue to use the loop as if the fork didn't happen, right? Yes, everything should be fine. I'll rephrase my question: do you think there is a way (and need) to at least throw a warning in the master process that the fork has failed (without monkey patching os.fork() which is not an option)?

> I was thinking only in the child. The parent should be able to continue to use the loop as if the fork didn't happen, right?

Yes, everything should be fine.

I'll rephrase my question: do you think there is a way (and need) to at least throw a warning in the master process that the fork has failed (without monkey patching os.fork() which is not an option)?

History
Date	User	Action	Args
2015-05-26 17:51:24	yselivanov	set	recipients: + yselivanov, gvanrossum, vstinner, christian.heimes, neologix, martius
2015-05-26 17:51:24	yselivanov	set	messageid: <1432662684.39.0.34715023867.issue21998@psf.upfronthosting.co.za>
2015-05-26 17:51:24	yselivanov	link	issue21998 messages
2015-05-26 17:51:24	yselivanov	create