[issue22007] sys.stdout.write on Python 2.7 is not EINTR safe

Piotr Dobrogost added the comment: @hypo Is there any reason you keep this PEP "secret" :) by not mentioning it on bug 18885? -- nosy: +piotr.dobrogost ___ Python tracker ___ __

[issue22007] sys.stdout.write on Python 2.7 is not EINTR safe

Changes by Charles-François Natali : -- resolution: -> duplicate stage: needs patch -> resolved status: open -> closed superseder: -> handle EINTR in the stdlib ___ Python tracker

[issue22007] sys.stdout.write on Python 2.7 is not EINTR safe

STINNER Victor added the comment: I'm interested to work on all EINTR issues, including Python 2. I'm working on a new PEP with Charles-François Natali to address *all* EINTR at once in Python 3.5. If the PEP is accepted, we may fix some EINTR issues on Python 2. Some changes change the behavi

[issue22007] sys.stdout.write on Python 2.7 is not EINTR safe

Ned Deily added the comment: I also can reproduce this on Linux with Python 2.7 but not with 3.4 which uses a different io system. So the question is: is anyone interested in addressing this for Python 2 file objects? -- nosy: +gregory.p.smith stage: -> needs patch title: sys.stdout.