[Python-Dev] iconv codec

M.-A. Lemburg mal@lemburg.com
Mon, 31 Mar 2003 11:38:02 +0200

Hye-Shik Chang wrote:
> On Mon, Mar 31, 2003 at 09:42:50AM +0200, M.-A. Lemburg wrote:
>>Since the introduction of the iconv codec there have been numerous
>>bug reports related to the codec and the lack of cross platform
>>support for it (ranging from: the codec doesn't compile and the
>>codec doesn't support standard names for common encodings to
>>core dumps in the linking phase).
>>I'd like to question whether the codec is really ready for prime
>>time yet. Right now it causes people more trouble than it does
>>any good.
> iconv_codec NG is ready to submit to SF. I think the newer
> implementation can resolve many of the patch reports. 

Are you sure ? As I mentioned in my mail, most problems
seem to be related to the platform's iconv implementation,
not so much to the Python one.

> I'll submit
> it in a few days. If you have a time, you can review my patches
> before my submission. 

Sorry, no time for that. I'm heading off to Python UK today.

> The patch includes ko, zh_CN, zh_TW codecs, also.
> A note about another problems on the current iconv_codec:
> http://fallin.lv/cvs/~checkout~/py-multibytecodec/reports/iconv.1
> The multibytecodecs which is in my patch submission queue:
> http://fallin.lv/distfiles/py-multibytecodec-030331.tar.gz
>>OTOH, without some field testing the codec will never get into
>>shape for prime time, so perhaps it would be better to only
>>enable it via a configure option or make a failure to compile
>>the codec as painless as possible.
> I agree.

Marc-Andre Lemburg

Professional Python Software directly from the Source  (#1, Mar 31 2003)
 >>> Python/Zope Products & Consulting ...         http://www.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
Python UK 2003, Oxford:                                     one day left
EuroPython 2003, Charleroi, Belgium:                        85 days left