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 brian.curtin, eric.araujo, jldm, r.david.murray, vstinner
Date 2010-12-03.13:53:43
SpamBayes Score 0.00011724941
Marked as misclassified No
Message-id <1291384425.87.0.327206190455.issue10197@psf.upfronthosting.co.za>
In-reply-to
Content
Ah, I did not realize that getstatusoutput was implemented using os.popen.  I thought it already used Popen.  Now, in python3, os.popen is in turn implemented using subprocess.Popen, so removing that level of indirection seems sensible.

The question that remains is, does removing the {} change the output obtained from a command sequence in any way?

Note that for backward compatibility you will need to re-munge the status code into C format.  Which makes me wonder if getoutput/getstatusoutput should just be documentationally deprecated instead.  (I never use them myself, FWIW)
History
Date User Action Args
2010-12-03 13:53:45r.david.murraysetrecipients: + r.david.murray, vstinner, eric.araujo, brian.curtin, jldm
2010-12-03 13:53:45r.david.murraysetmessageid: <1291384425.87.0.327206190455.issue10197@psf.upfronthosting.co.za>
2010-12-03 13:53:44r.david.murraylinkissue10197 messages
2010-12-03 13:53:43r.david.murraycreate