[Python-Dev] Re: let's not stretch a keyword's use unreasonably,
_please_...
Aahz
aahz at pythoncraft.com
Sat Oct 25 19:25:15 EDT 2003
On Sat, Oct 25, 2003, Alex Martelli wrote:
>
> Or, we can make the _compiler_ aware of what is going on (and get just the
> same semantics as global) by accepting either a non-statement keyword
> (scope, as I suggested elsewhere) or a magicname for import, e.g.
> import __me__ as Barry suggested. Then __me__.x=23 can have just the
> same semantics as today "x=23" has if there is some "global x" somewhere
> around, and indeed it could be compiled into the same bytecode if __me__
> was sufficiently special to the compiler.
We've already got ``import __main__``; what does __me__ gain?
--
Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/
"It is easier to optimize correct code than to correct optimized code."
--Bill Harlan
More information about the Python-Dev
mailing list