[Python-Dev] Scope object (Re: nonlocals() function?)
Antoine Pitrou
solipsis at pitrou.net
Tue Apr 6 01:35:24 CEST 2010
More information about the Python-Dev mailing list
Tue Apr 6 01:35:24 CEST 2010
- Previous message: [Python-Dev] Scope object (Re: nonlocals() function?)
- Next message: [Python-Dev] Scope object (Re: nonlocals() function?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Greg Ewing <greg.ewing <at> canterbury.ac.nz> writes: > > Maybe it would be better to deprecate globals() and locals() > and replace them with another function called something like > scope(). It is useful to distinguish between globals (i.e., module-level variables) and locals, so replacing them with scope() would not be better IMO. > It would return a mapping object that looks up > names in the current scope. It could also improve on locals() > by being writable. If you can prove that making locals() (or its replacement) writable doesn't complicate the interpreter core too much, then why not. Otherwise -1 :-) Regards Antoine.
- Previous message: [Python-Dev] Scope object (Re: nonlocals() function?)
- Next message: [Python-Dev] Scope object (Re: nonlocals() function?)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list