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 ezio.melotti, lemburg, spatz123, vstinner
Date 2011-09-21.11:20:51
SpamBayes Score 8.714412e-08
Marked as misclassified No
Message-id <4E79C879.50708@egenix.com>
In-reply-to <1316278067.86.0.927795690805.issue12508@psf.upfronthosting.co.za>
Content
The final parameter is an extension to the decoder API signature,
so it's not surprising that not all codecs implement it.

The ones that do should use it for all calls, since that way
the actual consumed number of bytes is correctly reported
back to the StreamReader instance.

Note: The parameter name "final" is a bit misleading. What happens
is that the number of bytes consumed by the decoder were previously
always reported as len(buffer), since the C API for decoders did
not provide a way to report back the number of bytes consumed.
This was changed when stateful decoders were added to the C API,
since these do allow reporting back the consumed bytes. A more
appropriate name for the parameter would have been
"report_bytes_consumed".
History
Date User Action Args
2011-09-21 11:20:52lemburgsetrecipients: + lemburg, vstinner, ezio.melotti, spatz123
2011-09-21 11:20:51lemburglinkissue12508 messages
2011-09-21 11:20:51lemburgcreate