➜

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 Adam.Bishop, Christian H, christian.heimes, gvanrossum, martius, neologix, pitrou, vstinner, yselivanov
Date 2017-06-28.20:08:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwZ0eH0YyRVPE7UBNmzsNTUMxuaYggT2R7-xtwuDQWkmbQ@mail.gmail.com>
In-reply-to <1498676536.13.0.073721516389.issue21998@psf.upfronthosting.co.za>
Content 
> The most reasonable IMHO would be for it to mark the event loop "broken" (or closed?) in the child, to forbid any further use.

Hum, the problem is that Python cannot guess if the event loop will be
used in the child or the parent process :-/ The problem only occurs
when the event loop is used in the two processes, no?
History
Date User Action Args
2017-06-28 20:08:16vstinnersetrecipients: + vstinner, gvanrossum, pitrou, christian.heimes, neologix, yselivanov, Adam.Bishop, martius, Christian H
2017-06-28 20:08:16vstinnerlinkissue21998 messages
2017-06-28 20:08:16vstinnercreate