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 gregory.p.smith
Recipients barry, ethan.furman, gregory.p.smith, r.david.murray, takluyver
Date 2015-01-28.23:39:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ethan: check_output combines them when stdout=subprocess.STDOUT is passed (
Never pass stdout=PIPE or stderr= PIPE to call() or check*() methods as
that will lead to a deadlock when a pipe buffer fills up.  check_output()
won't even allow you pass in stdout as it needs to set that to PIPE
internally, but you could still do the wrong thing and pass stderr=PIPE
without it warning you.

the documentation tells people not to do this.  i don't recall why we
haven't made it warn or raise when someone tries.  (but that should be a
separate issue/change)

On Wed Jan 28 2015 at 3:30:59 PM Ethan Furman <>

> Ethan Furman added the comment:
> I haven't checked the code, but does check_output and friends combine
> stdout and stderr when ouput=PIPE?
> ----------
> _______________________________________
> Python tracker <>
> <>
> _______________________________________
Date User Action Args
2015-01-28 23:39:47gregory.p.smithsetrecipients: + gregory.p.smith, barry, r.david.murray, ethan.furman, takluyver
2015-01-28 23:39:47gregory.p.smithlinkissue23342 messages
2015-01-28 23:39:47gregory.p.smithcreate