[New-bugs-announce] [issue32871] Interrupt .communicate() on SIGTERM/INT

Victor Porton report at bugs.python.org
Sun Feb 18 16:41:07 EST 2018


New submission from Victor Porton <porton at narod.ru>:

At https://docs.python.org/3/library/subprocess.html there is said nothing about what happens if our Python program terminates (by SIGTERM or SIGINT) while waiting for .communicate().

I assume to do something in this situation is just forgotten.

Usually terminate of our program should also terminate the invoked script. It can be made by re-delivery SIGTERM/SIGINT or (on non-POSIX) by .terminate() method. Probably, it should be done by .terminate() method even on POSIX systems, to handle SIGTERM and SIGINT in the same way.

----------
components: Library (Lib)
messages: 312328
nosy: porton
priority: normal
severity: normal
status: open
title: Interrupt .communicate() on SIGTERM/INT
type: behavior
versions: Python 3.6

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32871>
_______________________________________


More information about the New-bugs-announce mailing list