On 5/25/07, Jim Jewett <[EMAIL PROTECTED]> wrote: > On 5/24/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > > It doesn't look like any kind of global flag passed to the interpreter > > would scale -- once I am using a known trusted contribution that uses > > a different character set than mine, I would have to change the global > > setting to be more lenient, and the leniency would affect all code I'm > > using. > > Are you still thinking about the single on/off switch? > > I agree that saying "Japanese identifiers are OK from now on" still > shouldn't turn on Cyrillic identifiers. I think the current > alternative boils down to some variant of > > python -idchars allowedchars.txt > > where allowedchars.txt would look something like > > > 0780..07B1 ; Thaana > > or > > 10000..100FA ; Linear_B plus some blanks I was too lazy to exclude > > (These lines are based on the unicode Scripts.txt, and use character > ranges instead of script names so that you can exclude certain symbols > if you want to.)
I still think such a command-line switch (or switches) is the wrong approach. What if I have *one* module that uses Cyrillic legitimately. A command-line switch would enable Cyrillic in *all* modules. Auditing code using a separate tool can be much more flexible. Organizations can establish their own conventions for flagging exceptions on a per-module basis. -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ 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
