[Python-3000] Support for PEP 3131
bwinton at latte.ca
Sat May 26 05:45:22 CEST 2007
Jim Jewett wrote:
>>> If you didn't realize it was using non-ASCII (or even that it
>>> could), and the author didn't warn you -- then that is an1
>>> appropriate time for the interpreter to warn you that things aren't
>>> as you expect.
>> I fail to see your point. Why should the interpreter warn you?
> Arbitrary Unicode identifier opens up the possibility of code that
> *looks* like ASCII, but isn't -- so I don't even realize that I missed
You already have that problem. Right now. And you've had it for at
least a year (assuming you installed 2.4.3 when it came out).
All screenshots taken on Python 2.4.3, Mac OSX 10.4 Intel.
So, what are you doing to mitigate this risk now, and why not do the
same thing when identifiers are allowed to be arbitrary Unicode?
More information about the Python-3000