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
bpo-35182: fix communicate() crash after child closes its pipes #17020
Conversation
…7020) When communicate() is called in a loop, it crashes when the child process has already closed any piped standard stream, but still continues to be running
Codecov Report
@@ Coverage Diff @@
## master #17020 +/- ##
=========================================
Coverage ? 82.13%
=========================================
Files ? 1951
Lines ? 580578
Branches ? 44252
=========================================
Hits ? 476847
Misses ? 94109
Partials ? 9622
Continue to review full report at Codecov.
|
please port it to 3.7 & 3.8 |
Hi, I'm hitting this issue in production. Is there anything I could do to help get this merged? |
can you resolve the test_subprocess.py merge conflict? |
that's ok, let's proceed with your PR |
thanks! other PR merged. :) |
…onGH-17020) (pythonGH-18117) When communicate() is called in a loop, it crashes when the child process has already closed any piped standard stream, but still continues to be running Co-authored-by: Andriy Maletsky <andriy.maletsky@gmail.com>
When communicate() is called in a loop, it crashes when the child process has already closed any piped standard stream, but still continues to be running. The fix is trivial.
https://bugs.python.org/issue35182