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 > something.
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. http://bwinton.latte.ca/temp/Python/File.png http://bwinton.latte.ca/temp/Python/Run.png http://bwinton.latte.ca/temp/Python/foo.py 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? Later, Blake. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
