On 5/24/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote: > > Much of my concerns could be addressed through the use of commandline, > > environment variable, or in-source code definitions of what are > > allowable identifier characters. Generally, in-source definitions (like > > the coding: directive) are the most flexible, but are the biggest pain > > for editors and IDEs (which may want to verify every identifier as it is > > being typed, etc.).
> Not sure (anymore) what problem you are trying to solve, but it might be > that the coding directive already *is* the solution. If you want to > constrain characters that you can use in a single source file, adding > a coding directive will automatically impose such a constraint (namely, > to the characters available in the encoding). Wanting to constrain identifiers is not the same as wanting to constrain all characters. > In particular, if you set the encoding to us-ascii, you have restricted > your source file to ASCII only. The stdlib is largely restricted to ASCII. I don't think I want (the vast majority of) the stdlib to grow a coding directive just to enforce this. I also don't want to lift that restriction and accidentally allow Kanji identifiers just because Löwis appears in a comment. -jJ _______________________________________________ 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
