[Jeremy]
> I don't think I buy your explanation that Python uses dynamic scope
> for resolving globals.
It's dynamic in the shallow (but real!) sense that it can't be determined to
which of {module scope, builtin scope} a global name resolves today until
runtime. Indeed, in
def f():
print len
the resolving scope for "len" may even change with each invocation of f(),
depending on who's playing games with the containing module's __dict__.
That's not "dynamic scoping" in the proper sense of the term, but it's sure
dynamic!
words-lead-to-more-words-so-become-one-with-the-essence-instead<wink>-ly
y'rs - tim
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