[issue43336] document whether io.TextIOBase.readline(size>0) will always read the full newline

Andrei Kulakov added the comment: I don't think it's incorrect right now, from the POV of internal data of the stream, there's 6 chars, from the POV of caller, 5 chars are read. So this can be interpreted as 2 chars are combined into 1 char read. On the other hand if TextIOBase was reading

[issue43336] document whether io.TextIOBase.readline(size>0) will always read the full newline

Christoph Anton Mitterer added the comment: I guess that the translation from CRLF to LF simply happens before the size restriction is enforced (which is good so, btw), so effectively it: will not *read* at most size characters from the stream, but *return* at most size characters from it

[issue43336] document whether io.TextIOBase.readline(size>0) will always read the full newline

Change by Terry J. Reedy : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43336] document whether io.TextIOBase.readline(size>0) will always read the full newline

Christoph Anton Mitterer added the comment: "a n > 0size" should have read "a size > 0" -- ___ Python tracker ___ ___

[issue43336] document whether io.TextIOBase.readline(size>0) will always read the full newline

New submission from Christoph Anton Mitterer : Hey. It would be nice if the following behaviour could be definitely clarified: When reading from a text stream with readline(size) with a n > 0size it says: "If size is specified, at most size characters will be read." Also, depending on the