[issue23342] run() - unified high-level interface for subprocess
Martin Panter
report at bugs.python.org
Sat Jan 31 10:46:32 CET 2015
Martin Panter added the comment:
Maybe you don’t want to touch the implementation of the “older high-level API” for fear of subtly breaking something, but for clarification, and perhaps documentation, would the old functions now be equivalent to this?
def call(***):
# Verify PIPE not in (stdout, stderr) if needed
return run(***).returncode
def check_call(***):
# Verify PIPE not in (stdout, stderr) if needed
run(***, check=True)
def check_output(***):
# Verify stderr != PIPE if needed
return run(***, check=True, stdout=PIPE)
If they are largely equivalent, perhaps simplify the documentation of them in terms of run(), and move them closer to the run() documentation.
Is it worth making the CalledProcessError exception a subclass of CompletedProcess? They seem to be basically storing the same information.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23342>
_______________________________________
More information about the Python-bugs-list
mailing list