Author vstinner
Recipients gvanrossum, martius, neologix, vstinner, yselivanov
Date 2015-02-17.14:12:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1424182358.75.0.201645146564.issue21998@psf.upfronthosting.co.za>
In-reply-to
Content
> It will (obviously) not work with python 3.4 since self._selector won't have an _at_fork() method.

asyncio doc contains:
"The asyncio package has been included in the standard library on a provisional basis. Backwards incompatible changes (up to and including removal of the module) may occur if deemed necessary by the core developers."

It's not the case for selectors. Even if it would be possible to implement selector._at_fork() in asyncio, it would make more sense to implement it in the selectors module.

@neologix: Would you be ok to add a *private* _at_fork() method to selectors classes in Python 3.4 to fix this issue?

I know that you are not a fan of fork, me neither, but users like to do crazy things with fork and then report bugs to asyncio :-)
History
Date User Action Args
2015-02-17 14:12:38vstinnersetrecipients: + vstinner, gvanrossum, neologix, yselivanov, martius
2015-02-17 14:12:38vstinnersetmessageid: <1424182358.75.0.201645146564.issue21998@psf.upfronthosting.co.za>
2015-02-17 14:12:38vstinnerlinkissue21998 messages
2015-02-17 14:12:38vstinnercreate