This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients gregory.p.smith
Date 2015-02-24.08:56:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1424768178.86.0.938424229154.issue23508@psf.upfronthosting.co.za>
In-reply-to
Content
The changes from http://bugs.python.org/issue10197 caused subprocess.getstatusoutput() to start returning a subprocess returncode style status for the child process instead of a POSIX style status.

before that bug's changes:

>>> getstatusoutput("exit 1")[0]
256
>>> getstatusoutput("kill -TERM $$")[0]
15

after that bug's changes:

>>> getstatusoutput("exit 1")[0]
1
>>> getstatusoutput("kill -TERM $$")[0]
-15

This behavior was entirely untested so it was missed when fixing issue10197.

Given the new behavior has shipped in a stable Python release starting with (I believe) 3.3.4 and all 3.4 releases I do not think it should be changed.

But we should document it with proper versionchanged notices.
History
Date User Action Args
2015-02-24 08:56:18gregory.p.smithsetrecipients: + gregory.p.smith
2015-02-24 08:56:18gregory.p.smithsetmessageid: <1424768178.86.0.938424229154.issue23508@psf.upfronthosting.co.za>
2015-02-24 08:56:18gregory.p.smithlinkissue23508 messages
2015-02-24 08:56:18gregory.p.smithcreate