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 gjb1002
Recipients benjamin.peterson, gjb1002, gvanrossum, pitrou, pjenvey, stutzbach
Date 2011-12-19.19:54:43
SpamBayes Score 4.0187076e-11
Marked as misclassified No
Message-id <>
> 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 really the purpose of standard error though? Heavy debug output, in my experience, is usually sent to standard output or to another file.

Also, did anyone ever complain about this as a problem, given it is the default behaviour of Python 2?

In my view the requirements of seeing errors when they happen, and guaranteeing that they will always be seen no matter what happens afterwards, should weigh more heavily than this.
Date User Action Args
2011-12-19 19:54:44gjb1002setrecipients: + gjb1002, gvanrossum, pitrou, pjenvey, benjamin.peterson, stutzbach
2011-12-19 19:54:44gjb1002setmessageid: <>
2011-12-19 19:54:43gjb1002linkissue13601 messages
2011-12-19 19:54:43gjb1002create