[issue17285] subprocess.check_output incorrectly state that output is always bytes

2013-03-19 Thread Gregory P. Smith
Changes by Gregory P. Smith : -- resolution: -> fixed stage: needs patch -> commit review status: open -> closed ___ Python tracker ___ _

[issue17285] subprocess.check_output incorrectly state that output is always bytes

2013-03-19 Thread Roundup Robot
Roundup Robot added the comment: New changeset f4accfad1bf6 by Gregory P. Smith in branch '3.3': clarifiy the documentation for issue17285. see also commit http://hg.python.org/cpython/rev/f4accfad1bf6 New changeset d31cab1dabae by Gregory P. Smith in branch 'default': clarifiy the documentation

[issue17285] subprocess.check_output incorrectly state that output is always bytes

2013-03-01 Thread Terry J. Reedy
Changes by Terry J. Reedy : -- nosy: +terry.reedy versions: +Python 3.4 -Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailin

[issue17285] subprocess.check_output incorrectly state that output is always bytes

2013-02-24 Thread R. David Murray
R. David Murray added the comment: IMO the statement should read "and return the stdout data". The point is that check_output calls Popen and accepts all its arguments except for stdout, which it handles itself and returns as the result. It would probably be good to then follow that up with

[issue17285] subprocess.check_output incorrectly state that output is always bytes

2013-02-24 Thread Baptiste Lepilleur
New submission from Baptiste Lepilleur: Documentation states: >>> help( subprocess.check_output ) check_output(*popenargs, timeout=None, **kwargs) Run command with arguments and return its output as a byte string. But the most common usage is: >>> subprocess.check_output( 'echo test', shell