[issue1395] py3k: duplicated line endings when using read(1)

[Christian Heimes]

Christian Heimes added the comment:

Guido van Rossum wrote:
> 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.

In my opinion the check for \r should only happen when os.linesep or
newline starts with \r. On Unix with standard newline the \r should be
treated as every other char.

Christian

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1395>
__________________________________