➜

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 lemburg
Recipients BreamoreBoy, Jim.Jewett, ezio.melotti, lemburg, martin.panter, vstinner
Date 2015-01-14.08:34:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <54B62A20.9050704@egenix.com>
In-reply-to <1421198478.4.0.622374085396.issue14014@psf.upfronthosting.co.za>
Content 
On 14.01.2015 02:21, Martin Panter wrote:
> 
> Martin Panter added the comment:
> 
> I don’t think this is appropriate. If you want to flush the underlying stream, then call its flush() method after calling reset(). The docstring only says it flushes the _codec’s_ buffers, not any buffers of the underlying stream, and it should not be the codec’s business to worry about lower level buffers.

Correct. That's the reason why the method is called .reset() and
not .flush().
History
Date User Action Args
2015-01-14 08:34:47lemburgsetrecipients: + lemburg, vstinner, ezio.melotti, BreamoreBoy, martin.panter, Jim.Jewett
2015-01-14 08:34:47lemburglinkissue14014 messages
2015-01-14 08:34:47lemburgcreate