On 6/12/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > Ok, but why need you then *Python* to tell you that the file has > non-ASCII identifiers? Just look inside the file, and see whether > you like its source code.
That is just what many users (including, in some environments, me) cannot do *because* of the extended charset. I can't see whether the I have an ASCII o or a Cyrillic o, because they look the same, even though they aren't. If the whole think is in Cyrillic, I may notice; if only a few identifiers are, I probably won't notice at least until I've already saved it (and possibly broken it, depending on how unicode-unaware my editor is). > I don't see why you need Python to *reject* > identifiers outside ASCII - a warning would be surely enough to > indicate to you that your policy was violated. A warning would indeed be sufficient. -jJ _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
