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 pitrou
Recipients georg.brandl, pakal, pitrou
Date 2009-12-19.18:07:15
SpamBayes Score 2.4068785e-07
Marked as misclassified No
Message-id <1261246078.3339.2.camel@localhost>
In-reply-to <1261242726.76.0.778810398945.issue7545@psf.upfronthosting.co.za>
Content
> But now the question remains what the default is -- "full buffering" is
> only meaningful with a specified buffer size.  The implementation seems
> to default to line buffering.

"full" buffering actually uses a default or custom buffer size when you
don't specify it. 4096 or 8192 usually (yes there's a heuristic :-)).

"full" buffering is the default for binary streams, as well as for text
streams which aren't a tty. text streams which are tty default to line
buffering.

(I admit full buffering is a confusing name; what could we use instead?
fixed-size buffering? chunk buffering?)
History
Date User Action Args
2009-12-19 18:07:17pitrousetrecipients: + pitrou, georg.brandl, pakal
2009-12-19 18:07:15pitroulinkissue7545 messages
2009-12-19 18:07:15pitroucreate