A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2001-July/016055.html below:

Defining Python Source Code Encodings

[Python-Dev] Re: PEP: Defining Python Source Code Encodings [Python-Dev] Re: PEP: Defining Python Source Code EncodingsM.-A. Lemburg mal@lemburg.com
Wed, 18 Jul 2001 09:36:50 +0200
"Martin v. Loewis" wrote:
> 
> > To be 8-bit clean it will have to use Latin-1 as fallback encoding
> > since this encoding assures the roundtrip safety (decode to Unicode,
> > then reencode).
> 
> No, that is not true. Any other 8-bit encoding that has all code
> points assigned (e.g. Latin-2, or KOI8-R) would also give you full
> round-trip encoding.

True. Still, Latin-1 gives you the best performance and is also
compatible with the unicode-ecsape encoding which is currently in
use.

I'll add a note about this to the PEP.

Thanks,
-- 
Marc-Andre Lemburg
CEO eGenix.com Software GmbH
______________________________________________________________________
Consulting & Company:                           http://www.egenix.com/
Python Software:                        http://www.lemburg.com/python/



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