On 3/9/06, Nick Coghlan <[EMAIL PROTECTED]> wrote: > Steven Elliott wrote: > > I'm interested in how builtins could be more efficient. I've read over > > some of the PEPs having to do with making global variables more > > efficient (search for "global"): > > http://www.python.org/doc/essays/pepparade.html > > But I think the problem can be simplified by focusing strictly on > > builtins. > > Unfortunately, builtins can currently be shadowed in the module global > namespace from outside the module (via constructs like "import mod; mod.str = > my_str"). Unless/until that becomes illegal, focusing solely on builtins > doesn't help - the difficulties lie in optimising builtin access while > preserving the existing name shadowing semantics.
Is there any practical way of detecting and flagging constructs like the above (remotely shadowing a builtin in another module)? I can't see a way of doing it (but I know very little about this area...). If it *is* possible, I'd say it's worth implementing at least a warning sooner rather than later - the practice seems questionable at best, and any progress towards outlawing it would help in work on optimising builtins. Paul. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
