PEP 3131: Supporting Non-ASCII Identifiers

Thorsten Kampe thorsten at thorstenkampe.de
Tue May 15 08:27:09 EDT 2007


* René Fleschenberg (Tue, 15 May 2007 14:04:07 +0200)
> Thorsten Kampe schrieb:
> > Because keywords are not meant meant to extended or manipulated or 
> > something 	similar by the programmers. Keywords are well known and only 
> > a limited set of words. That's why you can't use keywords as 
> > identifiers.
> 
> This is true for keywords, but not for the stdlib. Are you suggesting
> that the stdlib should be "internationalized"?

No, because it's the /Standard/ Library to be used by everyone. And 
the lowest common denominator is ASCII and English.
 
> > There really is no difference to allow strings or comments in non-
> > english languages and non-ASCII characters.
> 
> Comments in a non-English language are a bad idea.

No, they're not. It depends on the purpose of the code. For a lot of 
projects comments in English might be a bad idea.

> And of course there is a difference between strings (data) and
> identifiers (program logic).

It's not about identifiers but about identifiers' names. Identifiers' 
names are a kind of API where the programmers "plug in" their own 
individuality or nationality. Just like string data and comments. 
You're not supposed to understand nor read nor even display this code. 
If you are then it's the programmer's responsibility to enable you to 
do so.



More information about the Python-list mailing list