➜

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 yselivanov
Recipients aeros, asvetlov, benjamin.peterson, nanjekyejoannah, njs, vstinner, yan12125, yselivanov
Date 2019-11-13.21:32:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1573680752.01.0.86514300708.issue38692@roundup.psfhosted.org>
In-reply-to
Content 
We can merge this PR as is (Benjamin, thanks for working on this!), but I think that as soon as we merge it we should do some refactoring and deprecations.

The child watchers API has to go. It's confusing, painful to use, it's not compatible with third-party event loops. It increases the API surface without providing us with enough benefits.

What I propose:

* merge this watcher and try to use it as the default on modern Linuxes.  We don't document it.

* deprecate add_child_watcher and all child watcher classes in 3.9. Aim for removal in 3.11.  

In 3.9 we will use kqueue / pidfd / threads / winapis -- whatever is available, but we never use SIGCHLD by default.
History
Date User Action Args
2019-11-13 21:32:32yselivanovsetrecipients: + yselivanov, vstinner, benjamin.peterson, njs, asvetlov, yan12125, nanjekyejoannah, aeros
2019-11-13 21:32:32yselivanovsetmessageid: <1573680752.01.0.86514300708.issue38692@roundup.psfhosted.org>
2019-11-13 21:32:31yselivanovlinkissue38692 messages
2019-11-13 21:32:31yselivanovcreate