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 aeros
Recipients aeros, asvetlov, benjamin.peterson, nanjekyejoannah, njs, vstinner, yan12125, yselivanov
Date 2019-11-13.23:36:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> > 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.

> +1

Also, adding to this, the child watchers are one of the least used components of asyncio's public API. So, I think the deprecation and removal cost will be fairly minimal. See the GitHub code usage (includes exact copies of Lib/asyncio/, so there's some redundancy):

MultiLoopChildWatcher: (20 results, just added in 3.8)
ThreadedChildWatcher: (77 results, default unix child watcher, rarely used explicitly)
FastChildWatcher: (4,426 results)
SafeChildWatcher: (7,007 results)
All of asyncio usage: (599,131 results)
Date User Action Args
2019-11-13 23:36:39aerossetrecipients: + aeros, vstinner, benjamin.peterson, njs, asvetlov, yselivanov, yan12125, nanjekyejoannah
2019-11-13 23:36:39aerossetmessageid: <>
2019-11-13 23:36:39aeroslinkissue38692 messages
2019-11-13 23:36:38aeroscreate