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 amaury.forgeotdarc, christian.heimes, pitrou, severb
Date 2008-12-31.14:00:16
SpamBayes Score 3.5598025e-11
Marked as misclassified No
Message-id <1230732021.10858.14.camel@localhost>
In-reply-to <1230731344.27.0.696957951453.issue4263@psf.upfronthosting.co.za>
Content
> I feel that no matter what implementation algorithm BufferedWriter uses
> it shouldn't write smaller chunks of data than buffer's size or else the
> buffer is useless.

If you rewrite the above sentence using the word "statistically", then I
can agree :)
But if I look at e.g. the fwrite() manpage, I see no guarantee that the
stdio layer will never make a call to write() with a size smaller than
the buffer size. The buffered layer should be free to manage its buffer
in what it believes is the most efficient way. The only guarantee is
that it won't buffer more than max_buffer_size.

Anyway :) Practically, the test does work on both py3k and another
implementation, so I don't see any urgency to remove anything from it.
History
Date User Action Args
2008-12-31 14:00:18pitrousetrecipients: + pitrou, amaury.forgeotdarc, christian.heimes, severb
2008-12-31 14:00:17pitroulinkissue4263 messages
2008-12-31 14:00:16pitroucreate