A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2019-May/157759.html below:

[Python-Dev] [SPAM?] Re: PEP 558: Defined semantics for locals()

[Python-Dev] [SPAM?] Re: PEP 558: Defined semantics for locals() [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
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

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4