On Mon, Aug 18, 2008 at 12:24 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote: > I'm -1 on taking this approach this late in the release process. > > You are adding a completely new codec, which hasn't received enough > testing. Furthermore, the concept of relying on OS defined codecs is > not in line with our concept of shipping codecs that work on all > platforms, not just the OS where they happen to be available via > some system libraries (and then completely outside of our control). > > For 3.0, please just add aliases to the existing codecs and a > note that this is just a work-around to be able to build Python > on Mac OS X.
I see. I've uploaded a patch for option 1 in issue #1276. > For 3.1, we'll then have to add proper codecs for the missing > encodings, hopefully reusing the existing CJK mapping tables. I already have a patch that is implemented just as you describe. :) Hye-Shik _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
