A RetroSearch Logo

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

Search Query:

Showing content from http://mail.python.org/pipermail/python-list/2005-September/314238.html below:

Simpler transition to PEP 3000 "Unicode only strings"?

Simpler transition to PEP 3000 "Unicode only strings"? Simpler transition to PEP 3000 "Unicode only strings"?Dieter Maurer dieter at handshake.de
Wed Sep 21 14:39:41 EDT 2005
"Petr Prikryl" <PrikrylP at skil.cz> writes on Tue, 20 Sep 2005 11:21:59 +0200:
> ...
> The idea:
> =========
> 
> What do you think about the following proposal
> that goes the half way
> 
>   If the Python source file is stored in UTF-8 (or
>   other recognised Unicode file format), then the
>   encoding declaration must reflect the format or
>   can be omitted entirely. In such case, all
>   simple string literals will be treated as
>   unicode string literals.
>   
> Would this break any existing code?

Yes: modules that construct byte strings (i.e. strings
which should *not* be unicode strings).

Nevertheless, such a module may be stored in UTF-8.

More information about the Python-list 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