[Python-Dev] iconv codec

M.-A. Lemburg mal@lemburg.com
Mon, 31 Mar 2003 09:42:50 +0200


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.

Some examples:
https://sourceforge.net/tracker/?group_id=5470&atid=105470&func=detail&aid=675341
https://sourceforge.net/tracker/?group_id=5470&atid=105470&func=detail&aid=690309
https://sourceforge.net/tracker/?group_id=5470&atid=105470&func=detail&aid=712056
https://sourceforge.net/tracker/?group_id=5470&atid=105470&func=detail&aid=694431

The problem doesn't seem to be related to the code implementation
itself, but rather the varying quality of iconv implementations
out there.

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.

-- 
Marc-Andre Lemburg
eGenix.com

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:                                      1 days left
EuroPython 2003, Charleroi, Belgium:                        85 days left