[issue6445] Add check parameter to subprocess.Popen.communicate

2017-03-07 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- stage: test needed -> resolved status: pending -> closed ___ Python tracker ___

[issue6445] Add check parameter to subprocess.Popen.communicate

2016-05-08 Thread Martin Panter
Martin Panter added the comment: According to PEP 375, 3.1 was out on 27 June 2009, just before this report was opened (9 July). So perhaps OG7 wasn’t aware of check_output() at the time. But it sounds like they did want CalledProcessError to be raised. I suggest to close this, unless there

[issue6445] Add check parameter to subprocess.Popen.communicate

2015-05-19 Thread Martin Panter
Martin Panter added the comment: In the mean time, a subprocess.run() API has been added which can call communicate() and raise CalledProcessError in one step (depending on arguments). See Issue 23342. This might satisfy some use cases, but maybe adding the check functionality to the

[issue6445] Add check parameter to subprocess.Popen.communicate

2014-05-16 Thread akira
akira added the comment: subprocess.check_output() could be used in communicate() + check process exit status one-liners. It returns child process output (stdout) and raises an exception if the returncode is not zero. It is available since Python 2.7 (3.1) If you don't want to raise an error

[issue6445] Add check parameter to subprocess.Popen.communicate

2014-02-03 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: -BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6445 ___ ___

[issue6445] Add check parameter to subprocess.Popen.communicate

2010-08-01 Thread Mark Lawrence
Mark Lawrence breamore...@yahoo.co.uk added the comment: @OG7 this is unlikely to move unless you provide a patch that changes the code and the unit test. -- nosy: +BreamoreBoy stage: - unit test needed type: - feature request versions: +Python 3.2

[issue6445] Add check parameter to subprocess.Popen.communicate

2009-07-09 Thread OG7
New submission from OG7 ony...@users.sourceforge.net: communicate is often used in one-liners, but becomes a four-liner if you want to check the process exit status. Adding a check parameter would make it more convenient to get things right and write non-buggy code. The CalledProcessError