RetroSearch Browse

Mon Jan 12 10:37:31 EST 2004 · https://mail.python.org/pipermail/python-dev/2004-January/041950.html

On Mon, Jan 12, 2004 at 04:28:48PM +0100, M.-A. Lemburg wrote:
> Barry Warsaw wrote:
> >On Fri, 2004-01-09 at 18:39, Martin v. Loewis wrote:
> >>There won't be universal preference for any package that we provide,
> >>or, for any kind of change made to Python. Unfortunately, the message
> >>you quote is hearsay, so we don't know what the specific objections
> >>are.
> >
> >I don't expect there to be universal acceptance, but there should be
> >enough momentum to make cjkcodecs the one way to do it for the large
> >majority of users.
> >
> >But we still haven't heard any concrete objections, so you should go for
> >it.
> 
> +1
> 
> Users who want to use other codec packages can easily do so,
> installing them in packages and then redirecting Python to use
> these by patching encoding.aliases.aliases to point to the
> codecs in the package rather than Python's default one.
> 
> This is best done in sitecustomize.py.
> 

Thanks!

Then, I'll apply the patch into CVS if no strong objection is raised
until this Saturday.

Hye-Shik

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-January/041950.html below:

[I18n-sig] Re: [Python-Dev] CJKCodecs integration into Python