Message 149446 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	benjamin.peterson, docs@python, gjb1002, pitrou, pjenvey, stutzbach
Date	2011-12-14.13:07:42
SpamBayes Score	1.4398932e-05
Marked as misclassified	No
Message-id	<1323868045.3334.2.camel@localhost.localdomain>
In-reply-to	<1323832923.54.0.459905532497.issue13597@psf.upfronthosting.co.za>

Content
> 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? Until recently it wasn't possible to have an unbuffered text stream with the new io stack. Now it's possible in write-only mode, although the open() builtin hasn't been updated for it.

> 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?

Until recently it wasn't possible to have an unbuffered text stream with
the new io stack. Now it's possible in write-only mode, although the
open() builtin hasn't been updated for it.

History
Date	User	Action	Args
2011-12-14 13:07:43	pitrou	set	recipients: + pitrou, gjb1002, pjenvey, benjamin.peterson, stutzbach, docs@python
2011-12-14 13:07:42	pitrou	link	issue13597 messages
2011-12-14 13:07:42	pitrou	create