31 Mar
2003
31 Mar
'03
11:11 p.m.
Guido van Rossum
But given that it's only got a small audience, a 3rd party module would satisfy the need just as well, right?
The audience is actually quite large: any call to <unicodestr>.encode could invoke this codec, if Python does not provide a builtin codec. This includes, in particular, all CJK codecs. Together with a platform-specific codec wrapper for Windows and OS X, the need to package Python-specific CJK codecs (with the size and maintenance issues that come with them) might vanish. Regards, Martin