[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Geoffrey Bache added the comment: Thanks. I'm not sure what you've written about the "-u" flag is correct though currently. From experimenting I believe it changes buffering of stdout and stderr to line-buffering also when directed to file, i.e. it does affect the behaviour of the text-layer

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Roundup Robot added the comment: New changeset 19df72a77b39 by Antoine Pitrou in branch '3.2': Issue #13597: Fix the documentation of the "-u" command-line option, and wording of "What's new in Python 3.0" about standard streams. http://hg.python.org/cpython/rev/19df72a77b39 New changeset 1ab1

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Antoine Pitrou added the comment: > I also suggested changes to the documentation of the "-u" flag, and to > "What's New in Python 3.0", can someone look at that also? Sorry for having overlooked that. This should now be fixed as well. -- ___ Pytho

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Geoffrey Bache added the comment: The changes are good as far as they go, but they only affect the documentation of sys.stderr and sys.stdout. I also suggested changes to the documentation of the "-u" flag, and to "What's New in Python 3.0", can someone look at that also? -- __

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Antoine Pitrou added the comment: Should be ok now. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Roundup Robot added the comment: New changeset 313fa7ea6c79 by Antoine Pitrou in branch '3.2': Issue #13597: Improve documentation of standard streams. http://hg.python.org/cpython/rev/313fa7ea6c79 New changeset 7343730185a3 by Antoine Pitrou in branch 'default': Issue #13597: Improve documenta

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Antoine Pitrou added the comment: (I've opened issue13601 for the possible behaviour change) -- ___ Python tracker ___ ___ Python-bug

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Geoffrey Bache added the comment: Ooops, seems like I just ran into a bug in the bug tracker too, it seems to have backed out other people's changes. Restoring them... -- components: +IO nosy: +benjamin.peterson, pitrou, pjenvey, stutzbach versions: -Python 3.1, Python 3.4 __

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Geoffrey Bache added the comment: I would certainly be in favour of restoring the python 2.x behaviour, at least where standard error is concerned. When writing Python programs, it's important to see exceptions immediately, and not lose them entirely in some circumstances. I reported this as

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Antoine Pitrou added the comment: > 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 > > Was this an oversight in migrating stdin/out/err to the new io module? Unt

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Philip Jenvey added the comment: 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 Was this an oversight in migrating stdin/out/err to the new io module? -- n

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

Antoine Pitrou added the comment: We could force sys.stderr to be always line-buffered if that's better than the current settings. -- components: +IO nosy: +benjamin.peterson, pitrou, stutzbach versions: -Python 3.1, Python 3.4 ___ Python tracker

[issue13597] Improve documentation of stdout/stderr buffering in Python 3.x

New submission from Geoffrey Bache : The default buffering of standard output and standard error has changed in Python 3.x with respect to Python 2.x, and I have been unable to find decent documentation of either the current behaviour, or the change. (See also http://groups.google.com/group/c