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, martius, vstinner, yselivanov
Date 2014-12-01.15:35:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJJ2-LCJpc6Bw+eec++d5PQ3krnJBs7ggTvTC12-7NjbDg@mail.gmail.com>
In-reply-to <1417426189.2.0.628098298456.issue21998@psf.upfronthosting.co.za>
Content
How about not doing anything in the parent but in the child, closing the
selector and then the event loop?

On Mon, Dec 1, 2014 at 1:29 AM, Martin Richard <report@bugs.python.org>
wrote:

>
> Martin Richard added the comment:
>
> I said something wrong in my previous comment: removing and re-adding the
> reader callback right after the fork() is obviously subject to a race
> condition.
>
> I'll go for the monkey patching.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue21998>
> _______________________________________
>
History
Date User Action Args
2014-12-01 15:35:03gvanrossumsetrecipients: + gvanrossum, vstinner, yselivanov, martius
2014-12-01 15:35:02gvanrossumlinkissue21998 messages
2014-12-01 15:35:02gvanrossumcreate