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 r.david.murray
Recipients docs@python, josh.r, ncoghlan, r.david.murray, tim.golden, vstinner
Date 2014-10-14.21:23:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1413321832.56.0.885166414962.issue22635@psf.upfronthosting.co.za>
In-reply-to
Content
You are right, it did change in 3.3.4 (see issue 10197).  That change should not have been applied to 3.3, and obviously there was a missing test concerning the return code format.

At this point I think we are stuck with changing the documentation.  The new return code is both more convenient and more consistent with the rest of the subprocess module.  It is very unfortunate that it did not follow our normal backward compatibility rules, but we are stuck with the mistake now.
History
Date User Action Args
2014-10-14 21:23:52r.david.murraysetrecipients: + r.david.murray, ncoghlan, vstinner, tim.golden, docs@python, josh.r
2014-10-14 21:23:52r.david.murraysetmessageid: <1413321832.56.0.885166414962.issue22635@psf.upfronthosting.co.za>
2014-10-14 21:23:52r.david.murraylinkissue22635 messages
2014-10-14 21:23:52r.david.murraycreate