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/2002-July/026553.html below:

[Python-Dev] Re: PEP 263 - Defining Python Source Code Encodings

[Python-Dev] Re: PEP 263 - Defining Python Source Code Encodings [Python-Dev] Re: PEP 263 - Defining Python Source Code EncodingsGuido van Rossum guido@python.org
Mon, 15 Jul 2002 13:32:43 -0400
>        Note that Python identifiers are restricted to the ASCII
>        subset of the encoding, and thus need no further conversion
>        after step 4.
> 
> Could identifiers be produced according to the usual syntax (letters or
> underscore, then letters, digits and underscore), but without going to
> ASCII first?
[...]
> We should try not missing the opportunity, if it happens to exist now.

To the contrary, I wish GNU readline didn't call setlocale().
Allowing non-ASCII identifiers may eventually happen, but there are
lots of reasons why it's a bad idea (such as source code portability),
and tying such a proposal to this PEP is definitely the wrong thing.

--Guido van Rossum (home page: http://www.python.org/~guido/)




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