Skip to content

bpo-30418: Popen.communicate() always ignore EINVAL#2002

Merged
vstinner merged 1 commit intopython:masterfrom
vstinner:subprocess_einval
Jun 8, 2017
Merged

bpo-30418: Popen.communicate() always ignore EINVAL#2002
vstinner merged 1 commit intopython:masterfrom
vstinner:subprocess_einval

Conversation

@vstinner
Copy link
Member

@vstinner vstinner commented Jun 8, 2017

On Windows, subprocess.Popen.communicate() now also ignore EINVAL
on stdin.write() if the child process is still running but closed the
pipe.

On Windows, subprocess.Popen.communicate() now also ignore EINVAL
on stdin.write() if the child process is still running but closed the
pipe.
@vstinner
Copy link
Member Author

vstinner commented Jun 8, 2017

cc @eryksun

@vstinner vstinner merged commit d52aa31 into python:master Jun 8, 2017
@vstinner vstinner deleted the subprocess_einval branch June 8, 2017 15:30
vstinner added a commit that referenced this pull request Jun 8, 2017
On Windows, subprocess.Popen.communicate() now also ignore EINVAL
on stdin.write() if the child process is still running but closed the
pipe.
(cherry picked from commit d52aa31)
vstinner added a commit that referenced this pull request Jun 8, 2017
On Windows, subprocess.Popen.communicate() now also ignore EINVAL
on stdin.write() if the child process is still running but closed the
pipe.
(cherry picked from commit d52aa31)
vstinner added a commit that referenced this pull request Jun 8, 2017
On Windows, subprocess.Popen.communicate() now also ignore EINVAL
on stdin.write() if the child process is still running but closed the
pipe.
(cherry picked from commit d52aa31)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant