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
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