➜

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 cameron
Recipients amaury.forgeotdarc, cameron, docs@python, eric.araujo, georg.brandl, python-dev, techtonik, terry.reedy, vstinner
Date 2012-01-14.03:34:58
SpamBayes Score 0.02223518
Marked as misclassified No
Message-id <1326512100.05.0.755740049401.issue11633@psf.upfronthosting.co.za>
In-reply-to
Content 
Putting the wording into 2.7 might be nice, but I thought it was in bugfix only mode.

Regarding UNIX only, I'd avoid it; any file may be buffered in almost any way on any platform. Saying an explicit flush call may be necessary for immediate output is _not_ UNIX only and would be very misleading. Remembering that ~UNIX != Windows.

Telling users to explicitly call flush to ensure immediate output where that is necessary ensures portable coding (or ought to, user pigheadedness discounted:-)
History
Date User Action Args
2012-01-14 03:35:00cameronsetrecipients: + cameron, georg.brandl, terry.reedy, amaury.forgeotdarc, vstinner, techtonik, eric.araujo, docs@python, python-dev
2012-01-14 03:35:00cameronsetmessageid: <1326512100.05.0.755740049401.issue11633@psf.upfronthosting.co.za>
2012-01-14 03:34:59cameronlinkissue11633 messages
2012-01-14 03:34:58cameroncreate