New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
py3k: child process don't inherit stdout / stderr on Windows #53026
Comments
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. |
("doesn't work" means that the example doesn't print anything) |
It's just under Windows, right? |
It works on Linux. I suppose that the issue is specific to Windows. |
Recent change of subprocess in py3k, I don't know if it's related: r78946. |
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 :-) |
Looks fine to me. The first line of the test comment has "if" instead of "is" but you could fix that on checkin. |
Fixed by r81403 (py3k). Even if the issue is a regression specific to 3.x, I backported the new test in 3.1: r81408. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: