[Python-3000] Support for PEP 3131

tomer filiba tomerfiliba at gmail.com
Sun May 13 17:33:08 CEST 2007

[Guillaume Proux]
> In this respect, I strongly believe that support non-ASCII identifiers
> as proposed by PEP3131 would improve a number of things:
> - discussion and uptake of python in "non-ascii" countries
> - ability for children to learn programming in their own language (I
> started programming at 7 years old and would have been very disturbed
> if I could not use my own language to type in programs)
> - increase of the number of new "interesting" packages from non-ascii countries
> - ability for local programmers and local companies to provide
> "bridges" between international (english) APIs and local APIs.
> - Increase the number of python users (from 7 to 77 years old)

well, i myself am a native hebrew speaker, so i'm quite sensitive
to text-direction issues with all sorts of editors. to this day, i haven't
seen a single editor that handles RTL/LTR transitions correctly,
including microsoft word.

when you start mixing LTR and RTL texts, it's asking for trouble:
שם_משפחה = "doe"
גיל = 5

i don't know how that would render on your machine, but on mine it says:
shem_mishpacha = "doe"
5 = gil   # looks reversed, but it's actually correct (!!)

so that basically rules out using hebrew, arabic and farsi from being
used as identifier, and the list is not complete.

now, since not all languages can be used, why bother supporting only some?
and if my library exposes a function with a chinese name, how would you
be able to invoke it without a chinese keyboard?

you'd do better with a translator sitting between the interpreter
and the editor.


More information about the Python-3000 mailing list