[issue13601] sys.stderr should always be line-buffered

Nick Coghlan added the comment: This question came up today in the context of the final line of a traceback output potentially being missing from stderr if the closing flush of the standard streams is missed for any reason. That's not going to be a common scenario (as far as I know it was an e

[issue13601] sys.stderr should always be line-buffered

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue13601] sys.stderr should always be line-buffered

Nick Coghlan added the comment: Changing the target version and summarising my understanding of the status quo: "python3": sys.stderr is line buffered at both the TextIOWrapper layer and may be fully buffered at the binary BufferedWriter layer if the output is redirected to a file "python3 -u"

[issue13601] sys.stderr should always be line-buffered

Terry J. Reedy added the comment: A month after this discussion, the flush keyword was added to print, which cover partial lines sent to either stdout or stderr via print. https://bugs.python.org/issue13761 -- ___ Python tracker

[issue13601] sys.stderr should always be line-buffered

Terry J. Reedy added the comment: As I read this, there was agreement that the status quo is sufficient. That would imply that this should be closed. Correct? -- nosy: +terry.reedy ___ Python tracker ___

[issue13601] sys.stderr should always be line-buffered

Geoffrey Bache added the comment: I think we all agree line-buffering is sufficient, so I change the title. -- title: sys.stderr should be unbuffered (or always line-buffered) -> sys.stderr should always be line-buffered ___ Python tracker