[Python-Dev] [SPAM?] Re: PEP 558: Defined semantics for locals()
Greg Ewing
greg.ewing at canterbury.ac.nz
Tue May 28 20:23:14 EDT 2019
More information about the Python-Dev mailing list
Tue May 28 20:23:14 EDT 2019
- Previous message (by thread): [Python-Dev] PEP 558: Defined semantics for locals()
- Next message (by thread): [Python-Dev] [SPAM?] Re: PEP 558: Defined semantics for locals()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Terry Reedy wrote: > 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. Yes, I understand *what's* happening, but not *why* it was designed that way. Would it really be probihitively expensive to create a fresh dict each time? -- Greg
- Previous message (by thread): [Python-Dev] PEP 558: Defined semantics for locals()
- Next message (by thread): [Python-Dev] [SPAM?] Re: PEP 558: Defined semantics for locals()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list