PEP 3131: Supporting Non-ASCII Identifiers

Thorsten Kampe thorsten at thorstenkampe.de
Tue May 15 09:10:54 EDT 2007


* René Fleschenberg (Tue, 15 May 2007 14:57:45 +0200)
> Stefan Behnel schrieb:
> > You're not trying to suggest that writing code in a closed area project is a
> > bad habit, are you?
> 
> I think that the idea that you know today, with 100% certainty, that all
> parts of your closed area project will stay closed forever is an
> illusion and thus a bad idea, yes.
> 
> > What would be bad about allowing a project to decide about the best and
> > clearest way to name identifiers? 
> 
> That very same argument could be used to allow all sorts of "strange
> stuff" in Python like gotos and worse. What would be bad about allowing
> a project to decide about how to do flow control, especially if you
> never get in touch with it?

GOTOs are not understable. Identifiers in foreign languages are 
perfectly understable. Just not to you.

For coding problems better solutions (approaches) exist than using 
GOTOs (procedural programming, modules). For identifier naming 
problems it's not a better approach to stick to English or ASCII. It's 
just a different approach.



More information about the Python-list mailing list