Jan. 23, 2016
8:03 p.m.
Guido van Rossum <guido@...> writes:
I've never liked the use of "late binding" in this context. The behavior is totally standard for closures that use mutable values.
I wonder if the problem isn't that "binding" is a term imported from a different language philosophy, and the idea there is just fundamentally different from Python's philosophy about variables.
I think my point is that even if "late binding" is the best term for Python's symbol resolution scheme, it may not be optimal to use it as an explanation for this particular closure behavior, since all languages with mutable closures behave in the same manner (and most of them would be classified as "early binding" languages). Stefan Krah