[issue26534] subprocess.check_output with shell=True ignores the timeout

2019-06-30 Thread Gregory P. Smith
Change by Gregory P. Smith : -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed superseder: -> subprocess.run timeout does not function if shell=True and capture_output=True ___ Python tracker

[issue26534] subprocess.check_output with shell=True ignores the timeout

2019-06-27 Thread haizaar
Change by haizaar : -- nosy: +haizaar ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26534] subprocess.check_output with shell=True ignores the timeout

2018-02-16 Thread Fangyi Zhou
Change by Fangyi Zhou : -- nosy: +fangyizhou ___ Python tracker ___ ___

[issue26534] subprocess.check_output with shell=True ignores the timeout

2017-04-24 Thread Martin Panter
Martin Panter added the comment: Issue 5115 is already open with patch that has an alternative API to the low-level “killpg” method. It also has a Windows implementation and tests. I suggest to focus this bug on the higher-level “kill_group” option. -- dependencies: +Extend

[issue26534] subprocess.check_output with shell=True ignores the timeout

2017-04-24 Thread Martin Panter
Martin Panter added the comment: I don’t know enough about process groups and sessions to properly review, but some things that stand out: * Patch is missing documentation and tests * If the “killpg” just wraps os.killpg, perhaps adding the method is not justified * Are there any race

[issue26534] subprocess.check_output with shell=True ignores the timeout

2016-03-10 Thread Daniel Shaulov
New submission from Daniel Shaulov: Basically - subprocess.check_output("ping localhost", shell=True, timeout=5) Will hang forever. What happens is that subprocess.run times out on communicate, sends SIGKILL *to the shell* and then calls communicate again without the timeout. But nothing