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 davidsarah
Recipients David.Sankel, amaury.forgeotdarc, christian.heimes, christoph, davidsarah, ezio.melotti, hippietrail, lemburg, mark, pitrou, santoso.wijaya, ssbarnea, terry.reedy, tim.golden, tzot, v+python, vstinner
Date 2011-03-26.19:22:48
SpamBayes Score 4.0540863e-06
Marked as misclassified No
Message-id <1301167372.36.0.54449771408.issue1602@psf.upfronthosting.co.za>
In-reply-to
Content
Glenn wrote:
> So if flush checks that bit, maybe TextIOWriter could just call buffer.flush, and it would be fast if clean and slow if dirty?

Yes. I'll benchmark how much overhead is added by the calls to flush; there's no point in breaking the abstraction boundary of BufferedWriter if it doesn't give a significant performance benefit. (I suspect that it might not, because Windows is very slow at scrolling a console, which might make the cost of flushing insignificant in comparison.)
History
Date User Action Args
2011-03-26 19:22:52davidsarahsetrecipients: + davidsarah, lemburg, terry.reedy, tzot, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, tim.golden, mark, christoph, ezio.melotti, v+python, hippietrail, ssbarnea, santoso.wijaya, David.Sankel
2011-03-26 19:22:52davidsarahsetmessageid: <1301167372.36.0.54449771408.issue1602@psf.upfronthosting.co.za>
2011-03-26 19:22:48davidsarahlinkissue1602 messages
2011-03-26 19:22:48davidsarahcreate