[Python-3000] Support for PEP 3131
tomerfiliba at gmail.com
Mon May 14 21:12:48 CEST 2007
as an english-second-language programmer, i'd really like to be able
to have unicode identifiers -- but my gut feeling is -- it will open the
door for a tower of babel.
once we have chinese, french and hindi function names, i'd be very
difficult to interoperate with third party libs. imagine i wrote my
code using twisted-he, while my client has installed twisted-fr...
kaboom? so the next step would be localization files that would
map standard names to locale-specific name? and then the
interpreter would use locale-dependent importing? we'll never see
the end of that. it would just grow more and more complicated.
english, or latin at least, is sufficient for programming. allowing for
more languages effectively means the creation of small, close
communities, rather than a global one.
-1 from me.
On 5/14/07, Daniel Stutzbach <daniel at stutzbachenterprises.com> wrote:
> On 5/13/07, Guillaume Proux <gproux+py3000 at gmail.com> wrote:
> > Is this a bijective translation ? How good is most people latin
> > character reading ability among Hebrew speakers? From the beginning, I
> > can tell from experience that Japanese people have great difficulties
> > in reading english or even transliterated japanese (which is never
> > good anyway because of homonyms)
> Unicode identifiers have been proposed before:
> Based on those threads, it seems that two empirical criteria that
> would sway many in the Python community are:
> 1) Evidence of positive use and results from languages that already
> support Unicode identifiers, such as Java, and/or
> 2) Support of Unicode identifiers in languages where the primary
> language author's native tongue is not based on Latin characters
> (notably Yukihiro Matsumoto's Ruby).
> Daniel Stutzbach, Ph.D. President, Stutzbach Enterprises LLC
More information about the Python-3000