PEP 3131: Supporting Non-ASCII Identifiers

[rurpy at yahoo.com]

On May 14, 9:53 am, Michel Claveau
<mcPas.De.S... at mclaveauPas.De.Spam.com> wrote:
> > - should non-ASCII identifiers be supported? why?
> > - would you use them if it was possible to do so? in what cases?
>
> Yes.
> And, more: yes yes yes
>
> Because:
>
> 1) when I connect Python to j(ava)Script, if the pages "connected"
> contains objects with non-ascii characters, I can't use it ; snif...
>
> 2) when I connect Python to databases, if there are fields (columns)
> with emphatic letters, I can't use class properties for drive these
> fields.  Exemples:
>      "cité" (french translate of "city")
>      "téléphone"  (for phone)
>
> And, because non-ASCII characters are possible, they are no-obligatory
> ; consequently guys (snobs?) want stay in pure-ASCII dimension will
> can.
>
> * sorry for my bad english *

Can a discussion about support for non-english identifiers (1)
conducted in a group where 99.9% of the posters are fluent
speakers of english (2), have any chance of being objective
or fair?

Although probably not-sufficient to overcome this built-in
bias, it would be interesting if some bi-lingual readers would
raise this issue in some non-english Python discussion
groups to see if the opposition to this idea is as strong
there as it is here.

(1) No quibbles about the distintion between non-english
and non-ascii please.
(2) Several posters have claimed non-native english speaker
status to bolster their position, but since they are clearly at
or near native-speaker levels of fluency, that english is not
their native language is really irrelevant.