[Python-Dev] [SPAM?] Re: PEP 558: Defined semantics for locals()
Terry Reedy
tjreedy at udel.edu
Mon May 27 09:12:40 EDT 2019
More information about the Python-Dev mailing list
Mon May 27 09:12:40 EDT 2019
- Previous message (by thread): [Python-Dev] [SPAM?] Re: PEP 558: Defined semantics for locals()
- Next message (by thread): [Python-Dev] PEP 558: Defined semantics for locals()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/27/2019 3:18 AM, Greg Ewing wrote: > Chris Angelico wrote: >> Except that it does. After calling locals() a second time, the result >> of the *first* call will be updated to reflect changes. > > Yeow. That's *really* unintuitive. There had better be an extremely > good reason for this behaviour. I believe that the situation is or can be thought of as this: there is exactly 1 function locals dict. Initially, it is empty and inaccessible (unusable) from code. Each locals() call updates the dict to a current snapshot and returns it. -- Terry Jan Reedy
- Previous message (by thread): [Python-Dev] [SPAM?] Re: PEP 558: Defined semantics for locals()
- Next message (by thread): [Python-Dev] PEP 558: Defined semantics for locals()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list