Barry Warsaw wrote But I do still think this is an appropriate patch for Python 2.3.x, since it really isn't a new feature. This change should be appropriate whether you continue to use the old (and unsupported) Korean and Chinese codecs, with the alternative (and supported) Japanese codec, or whether you decide to use the combined CJKCodecs package. At its heart the patch actually removes unnecessary dependencies on the separate Asian codec packages. Since they all provide aliases, this will make the Charset.py file independent of the codec package being used.
I guess the deciding thing (for me) is that code written to use Python
2.3.4 (and the new codec work) should work on Python 2.3.x (x<4). I
really don't want to see another repeat of the 2.2.2 fiasco (where
code written for 2.2.2 wouldn't work on 2.2.1 or 2.2, because of the
new True/False objects). I've seen far, far too much code that's had
True = 1
False = 0