PEP 3131: Supporting Non-ASCII Identifiers

Christophe Cavalaria chris.cavalaria at free.fr
Sun May 20 06:04:33 EDT 2007


Istvan Albert wrote:

> On May 19, 3:33 am, "Martin v. Löwis" <mar... at v.loewis.de> wrote:
> 
>> >    That would be invalid syntax since the third line is an assignment
>> > with target identifiers separated only by spaces.
>>
>> Plus, the identifier starts with a number (even though 6 is not DIGIT
>> SIX, but FULLWIDTH DIGIT SIX, it's still of category Nd, and can't
>> start an identifier).
> 
> Actually both of these issues point to the real problem with this PEP.
> 
> I knew about them (note that the colon is also missing) alas I
> couldn't fix them.
> My editor would could not remove a space or add a colon anymore, it
> would immediately change the rest of the characters to something
> crazy.
> 
> (Of course now someone might feel compelled to state that this is an
> editor problem but I digress, the reality is that features need to
> adapt to reality, moreso had I used a different editor I'd be still
> unable to write these characters).

The reality is that the few users who care about having chinese in their
code *will* be using an editor that supports them.




More information about the Python-list mailing list