[issue25942] subprocess.call SIGKILLs too liberally

Martin Panter report at bugs.python.org
Sun Nov 5 23:59:43 EST 2017


Martin Panter <vadmium+py at gmail.com> added the comment:

https://github.com/python/cpython/pull/4283 adds a secondary timeout, which defaults to 1 s when there is no main timeout. But this seems complicated and arbitrary. As I understand, the main use case discussed here was waiting without a timeout for a child that exits soon after the interrupt. But are there any practical use cases or demand for:

* Limiting the wait time after the interrupt (despite no timeout before the interrupt)?
* Customizing this additional timeout?

----------

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


More information about the Python-bugs-list mailing list