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 gvanrossum
Recipients gvanrossum, vstinner, yselivanov
Date 2014-09-15.18:09:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1410804575.82.0.800825922333.issue21998@psf.upfronthosting.co.za>
In-reply-to
Content
That sounds about right -- it's a doc issue. Let me propose a paragraph:

"""
NOTE: It is not safe to share an asyncio event loop between processes that are related by os.fork().  If an event loop exists in a process, and that process is forked, the only safe operation on the loop in the child process is to call its close() method.
"""

(I don't want to have to research what the various polling primitives do on fork(), so I don't want to suggest that it's okay to close the loop in the parent and use it in the child.)

A similar note should probably be added to the docs for the selectors module.
History
Date User Action Args
2014-09-15 18:09:35gvanrossumsetrecipients: + gvanrossum, vstinner, yselivanov
2014-09-15 18:09:35gvanrossumsetmessageid: <1410804575.82.0.800825922333.issue21998@psf.upfronthosting.co.za>
2014-09-15 18:09:35gvanrossumlinkissue21998 messages
2014-09-15 18:09:35gvanrossumcreate