This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients eryksun, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-05-21.08:21:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwb41yfAMs1-_+myFXB4D9zA2o_PndYQ9xcN28N0j_7FSQ@mail.gmail.com>
In-reply-to <1495340205.68.0.89214723272.issue30418@psf.upfronthosting.co.za>
Content
Basically, Windows EINVAL here looks like UNIX EPIPE. I agree to always
ignore it (remove the check on poll()).

I added the poll() check when I added the EINVAL test because I don't know
well Windows and I didn't know that write () can also fail with EINVAL if
the process is still running.

Your example makes it perfectly clear.

In short, Python must behave the same on Windows and UNIX on your example:
ignore errors on stdin.write().
History
Date User Action Args
2017-05-21 08:21:11vstinnersetrecipients: + vstinner, paul.moore, tim.golden, zach.ware, eryksun, steve.dower
2017-05-21 08:21:11vstinnerlinkissue30418 messages
2017-05-21 08:21:11vstinnercreate