Stefan Krah <stefan-use...@bytereef.org> added the comment: There are two cases:
1) stdin and stdout go to a tty: my_fgets() from Parser/myreadline.c does not handle the case where fgets() reads some characters followed by an EOF. One way to deal with this is to consider a sequence like 1234EOF an empty line. This is what the patch consider_1234EOF_empty_line.patch does and it fixes problem 1. [Another option would be to consider 1234EOF a line and insert a newline.] 2) stdout is not a tty: In this case, builtin_raw_input() uses PyFile_GetLine() to read from stdin. I'm not sure why this is the case. Perhaps 2) should be a separate issue. ---------- components: +Interpreter Core -IO keywords: +needs review, patch nosy: +skrah priority: -> normal stage: -> patch review title: raw_input() doesn't work as expected when it gets multiple ^D -> PyOS_Readline: treatment of "1234EOF"; behavior of builtin_raw_input type: -> behavior Added file: http://bugs.python.org/file16896/consider_1234EOF_empty_line.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6467> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
