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 pitrou
Recipients Adam.Bishop, Christian H, christian.heimes, gvanrossum, martius, neologix, pitrou, vstinner, yselivanov
Date 2017-06-28.19:02:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1498676536.13.0.073721516389.issue21998@psf.upfronthosting.co.za>
In-reply-to
Content
> Python 3.7 got as new os.register_at_fork() function. I don't know if it could help:

The most reasonable IMHO would be for it to mark the event loop "broken" (or closed?) in the child, to forbid any further use.

By the way, on Python 3 (which is pretty much required by asyncio), I really suggest using the "forkserver" method of multiprocessing, it removes a ton of hassle with inheritance through forking.
History
Date User Action Args
2017-06-28 19:02:16pitrousetrecipients: + pitrou, gvanrossum, vstinner, christian.heimes, neologix, yselivanov, Adam.Bishop, martius, Christian H
2017-06-28 19:02:16pitrousetmessageid: <1498676536.13.0.073721516389.issue21998@psf.upfronthosting.co.za>
2017-06-28 19:02:16pitroulinkissue21998 messages
2017-06-28 19:02:15pitroucreate