R. David Murray <rdmur...@bitdance.com> added the comment: Subprocess is throwing the correct exception, what it isn't doing is preserving stderr. The stderr output in question is not coming from the *subprocess* (the process hasn't been created yet). It would be nice if that stderr output could be added to the exception message, but that is not normally the way os errors are handled in python.
---------- nosy: +gregory.p.smith, r.david.murray title: subprocess.check_output throws wrong exception if non executable -> subprocess loses stderr information when _execute_child fails versions: +Python 3.2, Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12235> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
