Walter Dörwald added the comment:
That analysis seems correct to me.
Stateless and stream codecs were the original implementation. 2006 I
implemented incremental codecs: http://bugs.python.org/issue1436130
The intent was to have stateful codecs that can work with iterators and
generators.
Martin Panter added the comment:
I am certainly no expert, but this is how I understand the three different
kinds of codecs are used:
* Stateless codecs: str.encode(), bytes.decode(), etc
* Incremental codecs: TextIOWrapper, IncrementalNewlineDecoder
* Stream codecs: only stuff inside the
Nick Coghlan added the comment:
Unfortunately, a lot of these things aren't well defined in the docs because
they're not especially well defined, period. The codecs module works very well
if you stick to the common, well-tested paths (primarily the text encodings),
but it's complex enough
Nick Coghlan added the comment:
Regarding the 6 vs 4 interfaces, what's really needed there is a clearer
explanation of what functionality depends on each of the three interfaces
(basic, stream, incremental), so that a codec developer has a clearer
understanding of what won't work if they
New submission from Jan Kaliszewski:
To some extent, this issue is a follow-up of Issue 20132. It concerns some
parts of functionality + documentation of the 'codecs' module related to
registering custom codecs, especially non-string ones (i.e., codecs that
encode/decode between arbitrary
Jan Kaliszewski added the comment:
Sorry,
s/Issue 20132/Issue 19548/g
Issue 20132 is also related somehow, but here I ment that this is a follow-up
of Issue 19548; and Zoinkity's concerns I cited are also from Issue 19548, and
not from 20132.
--
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23232
___
___
Python-bugs-list
Changes by Ned Deily n...@acm.org:
--
nosy: +ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23232
___
___
Python-bugs-list mailing list
