[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Tim Golden added the comment: Closing this as won't fix. The code has been reimplemented and additional documentation has been added over at issue10197. Given that these are legacy functions, I don't propose to do any more here. -- resolution: -> wont fix status: open -> closed _

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Gregory P. Smith added the comment: If anybody using them in Python 3.3 is already depending upon them returning strings, changing it to return bytes will break their code... so that ship as unfortunately sailed. Changing that only in 3.4 would just cause churn and make code using this more d

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Changes by Tim Golden : Added file: http://bugs.python.org/file32483/issue9922.34.diff ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Changes by Tim Golden : -- assignee: -> tim.golden versions: +Python 3.3, Python 3.4 -Python 3.1, Python 3.2 ___ Python tracker ___ __

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Tim Golden added the comment: The code I've just committed to issue10197 means that the get[status]output functions now pass their (few) tests on all platforms. More by chance than judgement, that change employed universal_newlines which has the effect of forcing the output of check_output to

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Tim Golden added the comment: This has nearly been fixed by the rewrite of the get[status]output code under issue10197. There is an issue, though, with the use there of universal_newlines mode, which forces check_output to return a string rather than bytes. -- nosy: +tim.golden __

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Changes by Chris Rebert : -- nosy: +cvrebert ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Nick Coghlan added the comment: It is indeed unfortunate that these two functions weren't killed off in the Py3k transition instead of being migrated from the commands module to subprocess (their current implementation runs counter to the entire subprocess security design by implicitly invoki

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Antoine Pitrou added the comment: Well, getoutput and getstatusoutput are arguably ugly. However, since they are very high-level functions meant to quickly execute commands, returning str makes sense. You can't do anything smart with the output anyway, since stdout and stderr are intermingled

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Ross Lagerwall added the comment: getstatusoutput() is broken given that it doesn't work on windows yet it should. I'd also recommend leaving the behavior as is and deprecating the function (and getoutput() while we're at it). A related bug (#10197) also recommends deprecating getstatusoutput

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Ned Deily added the comment: I don't have a strong feeling about it but it seems to me that getstatusoutput is broken now so something should needs to be changed. If I understand your suggestion, adding a universal_newlines option to getstatusoutput similar to Popen, with a True (default) to

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

STINNER Victor added the comment: I think that it is now too late to change getstatusoutput() output type (str->bytes). I prefer Unicode and I think that most users will have to decode bytes to Unicode anyway. So the right solution is to be able to configure encoding and errors used by TextIO

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Changes by Ned Deily : Removed file: http://bugs.python.org/file18972/issue9922-31.patch ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Ned Deily added the comment: Update 31 backport patch to reflect revert of unittest method names prior to 3.1.3 release. -- Added file: http://bugs.python.org/file20023/issue9922-31-rev1.patch ___ Python tracker _

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Changes by Antoine Pitrou : -- nosy: +gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Changes by Ned Deily : Added file: http://bugs.python.org/file18972/issue9922-31.patch ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue9922] subprocess.getstatusoutput can fail with utf8 UnicodeDecodeError

Ned Deily added the comment: In Python 3, subprocess.Popen returns stdout as "bytes" rather than "string" so it seems reasonable that subprocess.getstatusoutput should do the same. >>> subprocess.Popen(['dd if=/dev/random bs=1024 count=1'], shell=True, >>> stdout=subprocess.PIPE).communicate(