[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Change by Benjamin Peterson : -- resolution: -> out of date stage: test needed -> resolved status: pending -> closed ___ Python tracker ___

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Irit Katriel added the comment: Since this is a python 2 only issue, should this issue be closed as out of date? -- nosy: +iritkatriel status: open -> pending ___ Python tracker

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Jun Wu added the comment: haypo: The file.__iter__ EINTR issue may be better discussed as a separate bug report. It's not related to stdin or EOF or Windows. Since we have some EINTR fixes for Python 2.7.4, I think it's reasonable to fix the remaining EINTR issues for 2.7.13+. If I have read

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

STINNER Victor added the comment: I don't see any simple solution to get a 100% reliable I/O stack on Python 2. Python 3.5 contains a pure Python implementation of the io module: _pyio.FileIO uses os.read() and os.write(). In Python 3.4 and older, the _pyio still used io.FileIO (implemented

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

STINNER Victor added the comment: Martijn Pieters: Sadly, Python 2 I/O are full of bugs in corner cases :-/ First of all, in most cases, Python 2 uses the libc for I/O, but the libc has known bugs including segfaults:

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Martijn Pieters added the comment: It looks like readahead was missed when http://bugs.python.org/issue12268 was fixed. -- ___ Python tracker ___

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Martijn Pieters added the comment: This bug affects all use of `file.__iter__` and interrupts (EINTR), not just sys.stdin. You can reproduce the issue by reading from a (slow) pipe in a terminal window and resizing that window, for example; the interrupt is not handled and a future call ends

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Don Hatch added the comment: I've reported the unfriendly input withholding that several people have observed and mentioned here as a separate bug: http://bugs.python.org/issue26290 . The symptom is different but I suspect it has exactly the same underlying cause (incorrect use of stdio) and

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Dan Kegel added the comment: Still present in python 2.7.9, but fixed in python 3.4.3. Also, in python 3.4.3, output is immediate, there seems to be no input buffering. -- nosy: +dankegel ___ Python tracker

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: -BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1633941 ___ ___

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Changes by Jaroslav Henner jaroslav.hen...@gmail.com: -- nosy: +jary ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1633941 ___ ___

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Ralph Corderoy ralph-pythonb...@inputplus.co.uk added the comment: This most certainly is a bug under Unix and an annoying one. Since the issue is with platform's stdio library is wrong; stdio is being used incorrectly. It would be nice to see it fixed in the 2.x line. I've two test

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Vetoshkin Nikita nikita.vetosh...@gmail.com added the comment: I guess http://bugs.python.org/issue1195 might be related -- nosy: +nvetoshkin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1633941

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Changes by Finkregh finkr...@mafia-server.net: -- nosy: +Finkregh ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1633941 ___ ___ Python-bugs-list

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Mark Lawrence breamore...@yahoo.co.uk added the comment: This is fixed in py3k but still exists in 2.7. -- nosy: +BreamoreBoy versions: +Python 2.7 -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1633941

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Éric Araujo mer...@netwok.org added the comment: Benjamin, is it too late too have this fixed in 2.7? -- nosy: +benjamin.peterson, merwok ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1633941

[issue1633941] for line in sys.stdin: doesn't notice EOF the first time

Changes by Fan Decheng fandech...@gmail.com: -- nosy: +r_mosaic ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1633941 ___ ___ Python-bugs-list