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 ned.deily
Recipients Thekent, ned.deily, roger.serwy, terry.reedy
Date 2012-05-27.21:12:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1338153152.05.0.135141105494.issue11820@psf.upfronthosting.co.za>
In-reply-to
Content
I didn't mean to imply anything about subprocess.check_output().  It works as expected, that is by explicitly intercepting anything written to the stdout of the forked subprocess and returning it as the call result.  What doesn't work is if you try a default subprocess.call(), for example.  The results are the same as os.system and for the same reason.  In a Posix terminal session:

$ python3.3
>>> import subprocess
>>> subprocess.call('pwd')
/Users/nad
0
>>> 

But in an IDLE shell window:
>>> import subprocess
>>> subprocess.call('pwd')
0
>>> 

That's confusing to users.  IDLE should handle that.
History
Date User Action Args
2012-05-27 21:12:32ned.deilysetrecipients: + ned.deily, terry.reedy, roger.serwy, Thekent
2012-05-27 21:12:32ned.deilysetmessageid: <1338153152.05.0.135141105494.issue11820@psf.upfronthosting.co.za>
2012-05-27 21:12:31ned.deilylinkissue11820 messages
2012-05-27 21:12:31ned.deilycreate