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 akira
Recipients akira, juj, vstinner
Date 2014-09-22.04:02:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Victor, the message in my patch is copied almost verbatim from the 
current subprocess' documentation [1]


People use `call(cmd, stdout=PIPE)` as a *broken* way to suppress 
output i.e., when they actually want `call(cmd, stdout=DEVNULL)`

The issue with `call(cmd, stdout=PIPE)` that it *appears* to work
if cmd doesn't produce much output i.e., it might work in tests but
may hang in production.

It is unrelated to check_output(), getstatusouptut() or getoutput().
Date User Action Args
2014-09-22 04:02:52akirasetrecipients: + akira, vstinner, juj
2014-09-22 04:02:52akirasetmessageid: <>
2014-09-22 04:02:52akiralinkissue22442 messages
2014-09-22 04:02:52akiracreate