RetroSearch Browse

Tue Jan 20 13:16:39 EST 2004 · https://mail.python.org/pipermail/python-dev/2004-January/042135.html

Martin v. Löwis wrote:
> M.-A. Lemburg wrote:
> 
>>> No. Instead, it applies uniformly to all codecs - so in some cases,
>>> users may see changes in the behaviour.
>>
>> Could you give an example ?
>>
>> The only change that I can think of is that setting up aliases
>> to override builtin codecs would start working and that's more
>> like a bug fix than a new feature.
> 
> Currently, if somebody defines a codec windows_1252.py, 
> foo.encode("windows_1252") uses this codec. With the proposed
> change, it uses cp1252.py. To see the behaviour change, no
> changes to the aliases list is necessary.

Thanks for the example. I agree that we should not backport the
change then.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Services directly from the Source  (#1, Jan 20 2004)
 >>> Python/Zope Consulting and Support ...        http://www.egenix.com/
 >>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::

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

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

[Python-Dev] Re: Changing codec lookup order