Staging
v0.8.1
https://github.com/python/cpython
Revision d3ae95e1e945ed20297e1c38ba43a18b7a868ab6 authored by Alex Rebert on 22 January 2020, 23:28:31 UTC, committed by Gregory P. Smith on 22 January 2020, 23:28:31 UTC
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>
1 parent 1f0f102
Raw File
Tip revision: d3ae95e1e945ed20297e1c38ba43a18b7a868ab6 authored by Alex Rebert on 22 January 2020, 23:28:31 UTC
bpo-35182: fix communicate() crash after child closes its pipes (GH-17020) (GH-18117)
Tip revision: d3ae95e
CODE_OF_CONDUCT.md
# Code of Conduct

Please note that all interactions on
[Python Software Foundation](https://www.python.org/psf-landing/)-supported
infrastructure is [covered](https://www.python.org/psf/records/board/minutes/2014-01-06/#management-of-the-psfs-web-properties)
by the [PSF Code of Conduct](https://www.python.org/psf/codeofconduct/),
which includes all the infrastructure used in the development of Python itself
(e.g. mailing lists, issue trackers, GitHub, etc.).

In general, this means that everyone is expected to be **open**, **considerate**, and
**respectful** of others no matter what their position is within the project.

back to top