[issue15049] line buffering isn't always

Antoine Pitrou added the comment: Indeed, line buffering on the read size would very slow (since you would have to read and decode one byte at a time from the raw stream to make sure you don't overshoot the line boundaries). -- ___ Python tracker

[issue15049] line buffering isn't always

R. David Murray added the comment: That makes sense. I'll add a mention of this to the 'open' docs that discuss the buffering parameter. -- assignee: -> r.david.murray components: +Documentation ___ Python tracker

[issue15049] line buffering isn't always

Martin v. Löwis added the comment: Without looking at the code, it seems that http://docs.python.org/release/3.1.5/library/io.html?highlight=io#io.TextIOWrapper gives the answer "If line_buffering is True, flush() is implied when a call to write contains a newline character." So, "line buff

[issue15049] line buffering isn't always

New submission from R. David Murray : rdmurray@hey:~/python/p32>cat bad.py This line is just ascii A second line for good measure. This comment contains undecodable stuff: "�" or "\\xe9" in "pass�"" cannot be decoded. The last line above is in latin-1, with an é inside those quotes