➜

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 njs
Recipients aeros, asvetlov, chris.jerdonek, njs, vstinner, yselivanov
Date 2020-05-10.01:53:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAPJVwBmR6yfaye5rvTskbN56SWzbn9h3cn6aOsA0mXJPZzR2WA@mail.gmail.com>
In-reply-to <[email protected]>
Content 
How do you know that your reproducer is showing the same bug, or anything
related to signals? IIUC subprocess waiting by default doesn't involve a
signal handler.

On Sat, May 9, 2020, 14:40 Chris Jerdonek <[email protected]> wrote:

>
> Chris Jerdonek <[email protected]> added the comment:
>
> > this seems like an awful lot of energy to spend on some code
> that's not even used by default.
>
> True, but it seems likely to me that this signals :) a deeper, more
> general issue about CPython / signals (which is why I spent time on it).
> For example, my reproducer script doesn't use MultiLoopWatcher. I'd like to
> see if it can be reproduced with signals other than SIGCHLD, too.
>
> ----------
>
> _______________________________________
> Python tracker <[email protected]>
> <https://bugs.python.org/issue38323>
> _______________________________________
>
History
Date User Action Args
2020-05-10 01:53:34njssetrecipients: + njs, vstinner, asvetlov, chris.jerdonek, yselivanov, aeros
2020-05-10 01:53:34njslinkissue38323 messages
2020-05-10 01:53:34njscreate