[issue8780] py3k: child process don't inherit stdout / stdout on Windows

Brian Curtin added the comment: Looks fine to me. The first line of the test comment has "if" instead of "is" but you could fix that on checkin. -- assignee: brian.curtin -> haypo ___ Python tracker _

[issue8780] py3k: child process don't inherit stdout / stdout on Windows

STINNER Victor added the comment: Ok, it *is* a regression introduced by r78946. Attached patch fixes the issue and adds a regression test. Add also the author of r78946 to the nosy list :-) -- keywords: +patch nosy: +gregory.p.smith Added file: http://bugs.python.org/file17430/subpro

[issue8780] py3k: child process don't inherit stdout / stdout on Windows

STINNER Victor added the comment: Recent change of subprocess in py3k, I don't know if it's related: r78946. -- ___ Python tracker ___ ___

[issue8780] py3k: child process don't inherit stdout / stdout on Windows

STINNER Victor added the comment: > It's just under Windows, right? It works on Linux. I suppose that the issue is specific to Windows. -- title: py3k: child process don't inherit stdout / stdout -> py3k: child process don't inherit stdout / stdout on Windows

[issue8780] py3k: child process don't inherit stdout / stdout

Antoine Pitrou added the comment: It's just under Windows, right? -- assignee: -> brian.curtin components: +Windows nosy: +brian.curtin, pitrou priority: normal -> critical ___ Python tracker _

[issue8780] py3k: child process don't inherit stdout / stdout

STINNER Victor added the comment: ("doesn't work" means that the example doesn't print anything) -- ___ Python tracker ___ ___ Python-

[issue8780] py3k: child process don't inherit stdout / stdout

New submission from STINNER Victor : The following code works on 2.6, 2.7 (trunk), 3.1, but not on py3k. import subprocess, sys subprocess.call([sys.executable, '-c', 'print("Hello World!")']) On py3k, sys.stdout and sys.stderr are equal to... None. I hope that it's a problem with my setup. -