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 vstinner
Recipients Arfrever, acassaigne, docs@python, gregory.p.smith, josh.r, ncoghlan, r.david.murray, tim.golden, vstinner
Date 2017-08-09.09:21:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1502270464.81.0.980131134285.issue22635@psf.upfronthosting.co.za>
In-reply-to
Content
IMHO it's too late to change *again* subprocess.getstatusoutput() behaviour. Otherwise, it would mean that a complex test like "if not((3, 4) <= sys.version_info < (3, 7))" would be needed to workaround the bug... Whereas right now, basically we only have to check if we are running on Python 3 or not. (Python 3.0-3.3 is almost not used in the wild.)

Instead we should just *document* the behaviour change using ".. versionchanged:: 3.4" in Doc/library/subprocess.rst.

Any volunteer to do that?
History
Date User Action Args
2017-08-09 09:21:04vstinnersetrecipients: + vstinner, gregory.p.smith, ncoghlan, tim.golden, Arfrever, r.david.murray, docs@python, acassaigne, josh.r
2017-08-09 09:21:04vstinnersetmessageid: <1502270464.81.0.980131134285.issue22635@psf.upfronthosting.co.za>
2017-08-09 09:21:04vstinnerlinkissue22635 messages
2017-08-09 09:21:04vstinnercreate