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 martin.panter
Recipients Mike Pomraning, SilentGhost, martin.panter, vstinner
Date 2016-01-01.20:21:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1451679701.23.0.0632022736801.issue25942@psf.upfronthosting.co.za>
In-reply-to
Content
The reported problem is when no timeout is given. Perhaps it would be sufficient to:

1. Kill the child if any exception happens when a timeout is enforced
2. Never kill the child when there is no timeout

If a timeout is specified, the current code is good enough, but if no timeout is specified, maybe we should just do the equivalent of:

with Popen(...) as p:
    return p.wait()
    # If interrupted, the context manager will wait again. If the interruption is due to a terminal-wide SIGINT, the child may also have been interrupted.

For comparison, the Posix system() function is supposed to ignore SIGINT and SIGQUIT (i.e. signals from the terminal). See the Gnu implementation: <https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/posix/system.c>.
History
Date User Action Args
2016-01-01 20:21:41martin.pantersetrecipients: + martin.panter, vstinner, SilentGhost, Mike Pomraning
2016-01-01 20:21:41martin.pantersetmessageid: <1451679701.23.0.0632022736801.issue25942@psf.upfronthosting.co.za>
2016-01-01 20:21:41martin.panterlinkissue25942 messages
2016-01-01 20:21:40martin.pantercreate