[issue22274] subprocess.Popen(stderr=STDOUT) fails to redirect subprocess stderr to stdout

2016-05-13 Thread Martin Panter
Martin Panter added the comment: Thanks for the patch Akira. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker

[issue22274] subprocess.Popen(stderr=STDOUT) fails to redirect subprocess stderr to stdout

2016-05-13 Thread Roundup Robot
Roundup Robot added the comment: New changeset 642933771fa5 by Martin Panter in branch '3.5': Issue #22274: Redirect stderr=STDOUT when stdout not redirected, by Akira Li https://hg.python.org/cpython/rev/642933771fa5 New changeset 5979e7aadd59 by Martin Panter in branch 'default': Issue

[issue22274] subprocess.Popen(stderr=STDOUT) fails to redirect subprocess stderr to stdout

2016-05-08 Thread Martin Panter
Martin Panter added the comment: I think this patch is pretty good. I will try to commit it in the next few days. -- nosy: +martin.panter versions: +Python 2.7, Python 3.5, Python 3.6 ___ Python tracker

[issue22274] subprocess.Popen(stderr=STDOUT) fails to redirect subprocess stderr to stdout

2016-05-08 Thread Akira Li
Akira Li added the comment: Updated the patch to address vadmium's review comments. -- versions: -Python 3.4 Added file: http://bugs.python.org/file42777/subprocess-stderr_redirect_with_no_stdout_redirect-2.diff ___ Python tracker

[issue22274] subprocess.Popen(stderr=STDOUT) fails to redirect subprocess stderr to stdout

2014-08-28 Thread Akira Li
Akira Li added the comment: Josh, on Windows, if at least one standard stream is replaced; all three hStdInput, hStdOutput, hStdError handles are provided (all-or-nothing). On POSIX, standard streams stdin (0), stdout (1), stderr (2) are always inherited from the parent. Each stream can be

[issue22274] subprocess.Popen(stderr=STDOUT) fails to redirect subprocess stderr to stdout

2014-08-25 Thread Akira Li
New submission from Akira Li: The following command should not produce any output but it does: $ ./python /dev/null -c 'import subprocess as S, sys; S.call([sys.executable, -c, import sys; print(42, file=sys.stderr)], stderr=S.STDOUT)' Its stdout is redirected to /dev/null. It starts a

[issue22274] subprocess.Popen(stderr=STDOUT) fails to redirect subprocess stderr to stdout

2014-08-25 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- nosy: +gregory.p.smith stage: - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22274 ___ ___

[issue22274] subprocess.Popen(stderr=STDOUT) fails to redirect subprocess stderr to stdout

2014-08-25 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22274 ___ ___

[issue22274] subprocess.Popen(stderr=STDOUT) fails to redirect subprocess stderr to stdout

2014-08-25 Thread Josh Rosenberg
Josh Rosenberg added the comment: Okay, dumb question: Is there a reason the Windows code explicitly initializes c2pwrite in the stdout not passed case, while the Linux code leaves it as -1? Windows doesn't look like it would have the problem (because c2pwrite is always set to a non-default

[issue22274] subprocess.Popen(stderr=STDOUT) fails to redirect subprocess stderr to stdout

2014-08-25 Thread STINNER Victor
Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22274 ___ ___ Python-bugs-list