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 vstinner
Recipients gvanrossum, vstinner, yselivanov
Date 2014-09-15.07:15:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1410765350.38.0.815482861443.issue21998@psf.upfronthosting.co.za>
In-reply-to
Content
> Is there a use case for sharing an event loop across forking?

I don't know if asyncio must have a builtin support for this use case. The minimum is to document the behaviour, or maybe even suggest a recipe to support it.

For example, an event loop of asyncio is not thread-safe and we don't want to support this use case. But I wrote a short documentation with code snippets to show how to workaround this issue:
https://docs.python.org/dev/library/asyncio-dev.html#concurrency-and-multithreading

We need a similar section to explain how to use asyncio with the os.fork() function and the multiprocesing module.
History
Date User Action Args
2014-09-15 07:15:50vstinnersetrecipients: + vstinner, gvanrossum, yselivanov
2014-09-15 07:15:50vstinnersetmessageid: <1410765350.38.0.815482861443.issue21998@psf.upfronthosting.co.za>
2014-09-15 07:15:50vstinnerlinkissue21998 messages
2014-09-15 07:15:50vstinnercreate