[issue1395] py3k: duplicated line endings when using read(1)
Guido van Rossum
report at bugs.python.org
Tue Nov 6 18:43:35 CET 2007
Guido van Rossum added the comment:
IMO you shouldn't read another chunk when the last character you've seen
is \r; instead, you should set a flag so that on the next read, you'll
ignore an initial \n. The flag should be made of the tell/seek state as
well.
(The problem with reading another character is that in interactive input
mode, this might force the user to type an entire second line.)
__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1395>
__________________________________
More information about the Python-bugs-list
mailing list