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
Date 2014-08-25.21:46:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1409003162.0.0.312391949761.issue22274@psf.upfronthosting.co.za>
In-reply-to
Content
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 subprocess with its
stderr redirected to stdout. See "Redirect subprocess stderr to
stdout" [1] on Stackoverflow.

[1] http://stackoverflow.com/questions/11495783/redirect-subprocess-stderr-to-stdout

I've uploaded a patch that fixes the issue on POSIX.

Please, run the provided test (in the patch), to see whether the code
should be fixed on Windows too (it might work as is there).

No documentation changes are required.

Please, review.
History
Date User Action Args
2014-08-25 21:46:02akirasetrecipients: + akira
2014-08-25 21:46:02akirasetmessageid: <1409003162.0.0.312391949761.issue22274@psf.upfronthosting.co.za>
2014-08-25 21:46:01akiralinkissue22274 messages
2014-08-25 21:46:01akiracreate