[Python-Dev] Stateful codecs [Was: str object going in Py3K]
Walter Dörwald
walter at livinglogic.de
Tue Feb 21 20:36:31 CET 2006
More information about the Python-Dev mailing list
Tue Feb 21 20:36:31 CET 2006
- Previous message: [Python-Dev] Stateful codecs [Was: str object going in Py3K]
- Next message: [Python-Dev] Stateful codecs [Was: str object going in Py3K]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hye-Shik Chang wrote: > On 2/19/06, Walter Dörwald <walter at livinglogic.de> wrote: >> M.-A. Lemburg wrote: >>> Walter Dörwald wrote: >>>> Anyway, I've started implementing a patch that just adds >>>> codecs.StatefulEncoder/codecs.StatefulDecoder. UTF8, UTF8-Sig, >>>> UTF-16, UTF-16-LE and UTF-16-BE are already working. >>> Nice :-) >> gencodec.py is updated now too. The rest should be manageble too. >> I'll leave updating the CJKV codecs to Hye-Shik though. > > Okay. I'll look whether how CJK codecs can be improved by the > new protocol soon. I guess it'll be not so difficult because CJK > codecs have a their own common stateful framework already. OK, here's the patch: bugs.python.org/1436130 (assigned to MAL). > BTW, CJK codecs don't have V yet. :-) Bye, Walter Dörwald
- Previous message: [Python-Dev] Stateful codecs [Was: str object going in Py3K]
- Next message: [Python-Dev] Stateful codecs [Was: str object going in Py3K]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list