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 gvanrossum
Recipients benjamin.peterson, gvanrossum, pitrou, pjenvey, stutzbach
Date 2011-12-14.15:29:53
SpamBayes Score 5.966758e-10
Marked as misclassified No
Message-id <>
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 newline.

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).

Maybe we need better command-line control to override the defaults?  Are there precedents e.g. in Bash flags?
Date User Action Args
2011-12-14 15:29:54gvanrossumsetrecipients: + gvanrossum, pitrou, pjenvey, benjamin.peterson, stutzbach
2011-12-14 15:29:54gvanrossumsetmessageid: <>
2011-12-14 15:29:54gvanrossumlinkissue13601 messages
2011-12-14 15:29:53gvanrossumcreate