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 asvetlov
Recipients aeros, asvetlov, vstinner, yselivanov
Date 2019-10-26.08:45:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
My non-LTS Ubuntu also has 5.3 kernel but I'm talking about the oldest supported RHEL/CentOS.

That's why pidfd_open() cannot be a single implementation. It's so new; my local man-pages system has not a record about the API yet (but the web has:

> If asyncio is only run from the main thread, FastChildWatcher is safe, fast and has low memory footprint, no?

Unfortunately, no. FastChildWatcher is safe if you can guarantee that no code executed in asyncio main thread AND thread pools spawn subprocesses. Otherwise, the whole Python process becomes broken by the race condition between FastChildWatcher and any other wait()/waitpid()/waitid() call.
Date User Action Args
2019-10-26 08:45:41asvetlovsetrecipients: + asvetlov, vstinner, yselivanov, aeros
2019-10-26 08:45:41asvetlovsetmessageid: <>
2019-10-26 08:45:41asvetlovlinkissue38591 messages
2019-10-26 08:45:41asvetlovcreate