[issue13601] sys.stderr should be unbuffered (or always line-buffered)

Geoffrey Bache added the comment: > I'm hesitant to make it line-buffered by default when directed to a > file, since this could significantly slow down a program that for some > reason produces super-voluminous output (e.g. when running a program > with heavy debug logging turned on). Is that

[issue13601] sys.stderr should be unbuffered (or always line-buffered)

Antoine Pitrou added the comment: Oops, I forgot the last two questions: > Maybe we need better command-line control to override the defaults? We already have -u to switch all stdio to unbuffered. This issue proposes to make stderr line-buffered/unbuffered by default, since it's less surprisi

[issue13601] sys.stderr should be unbuffered (or always line-buffered)

Antoine Pitrou added the comment: > Line-buffering should be good enough since in practice errors messages > are always terminated by a newline. What I think too. > I'm hesitant to make it line-buffered by default when directed to a > file, since this could significantly slow down a program th

[issue13601] sys.stderr should be unbuffered (or always line-buffered)

Changes by Geoffrey Bache : -- nosy: +gjb1002 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue13601] sys.stderr should be unbuffered (or always line-buffered)

Guido van Rossum added the comment: I *thought* I mimicked what C stdio did ~20 years ago... I'd be happy to follow what it does today if it changed or if I made a mistake. That said, IMO: Line-buffering should be good enough since in practice errors messages are always terminated by a newl

[issue13601] sys.stderr should be unbuffered (or always line-buffered)

New submission from Antoine Pitrou : In issue13597, Philip Jenvey points out: “I'm surprised to hear that stderr is line buffered by default. Historically stderr is never buffered (at least on POSIX) and for good reason: errors should be seen immediately” Recent changes to the IO stack should