Message149887
> 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:44 | gjb1002 | set | recipients:
+ gjb1002, gvanrossum, pitrou, pjenvey, benjamin.peterson, stutzbach |
2011-12-19 19:54:44 | gjb1002 | set | messageid: <1324324484.29.0.780076023192.issue13601@psf.upfronthosting.co.za> |
2011-12-19 19:54:43 | gjb1002 | link | issue13601 messages |
2011-12-19 19:54:43 | gjb1002 | create | |
|