[Python-Dev] let's not stretch a keyword's use unreasonably, _please_...
Alex Martelli
aleaxit at yahoo.com
Fri Oct 24 15:18:49 EDT 2003
More information about the Python-Dev mailing list
Fri Oct 24 15:18:49 EDT 2003
- Previous message: [Python-Dev] let's not stretch a keyword's use unreasonably, _please_...
- Next message: [Python-Dev] closure semantics
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Friday 24 October 2003 08:26 pm, Oren Tirosh wrote: ... > How about using the word 'global' to get the current module object? > A precedent for this is None which is on its way to becoming a keyword > to get that "particular object". > > A bit of parser magic would be required so global can still work > as a declaration for compatibility. Unfortunately I think Guido clarified in a previous post the amount of parser magic needed for that is excessive -- no lookahead allowed. If we managed to tweak the parser, we'd still have the issue of keyword inappropriateness -- and further stretching if we also want to use it to allow rebinding of outer-scope variables that AREN'T "global" in any sense whatsoever. So I'd much rather have 'scope' and no issue with parser magic... Alex
- Previous message: [Python-Dev] let's not stretch a keyword's use unreasonably, _please_...
- Next message: [Python-Dev] closure semantics
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list