A RetroSearch Logo

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

Search Query:

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

[Python-Dev] Re: Changing codec lookup order

[Python-Dev] Re: Changing codec lookup order [Python-Dev] Re: Changing codec lookup order"Martin v. Löwis" martin at v.loewis.de
Tue Jan 20 13:01:18 EST 2004
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.

Regards,
Martin


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4