[issue32871] Interrupt .communicate() on SIGTERM/INT

[Alexey Izbyshev]

Alexey Izbyshev  added the comment:

@ajk225 It may be useful to look at #25942 before working on this.

--
nosy: +izbyshev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32871] Interrupt .communicate() on SIGTERM/INT

[ajk225]

ajk225  added the comment:

Is this still open?  If so, can I take this on as my first issue?

--
nosy: +ajk225

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32871] Interrupt .communicate() on SIGTERM/INT

[Victor Porton]

New submission from Victor Porton :

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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com