The following test fails:
#!/usr/bin/env python
def f(*args):
"""
>>> t = 1, -1
>>> f(*map(lambda i: lambda: i, t))
[1, -1]
>>> f(*(lambda: i for i in t)) # -> [-1, -1]
[1, -1]
>>> f(*[lambda: i for i in t]) # -> [-1, -1]
[1, -1]
"""
alist = [a() for a in args]
print(alist)
if __name__ == '__main__':
import doctest; doctest.testmod()
In other words:
>>> t = 1, -1
>>> args = []
>>> for i in t:
... args.append(lambda: i)
...
>>> map(lambda a: a(), args)
[-1, -1]
>>> args = []
>>> for i in t:
... args.append((lambda i: lambda: i)(i))
...
>>> map(lambda a: a(), args)
[1, -1]
>>> args = []
>>> for i in t:
... args.append(lambda i=i: i)
...
>>> map(lambda a: a(), args)
[1, -1]
Expression
f = lambda: i
is equivalent to:Expression
g = lambda i=i: i
is equivalent to:i
is a free variable in the first case and it is bound to the function parameter in the second case i.e., it is a local variable in that case. Values for default parameters are evaluated at the time of function definition.Generator expression is the nearest enclosing scope (where
i
is defined) fori
name in thelambda
expression, thereforei
is resolved in that block:i
is a local variable of thelambda i: ...
block, therefore the object it refers to is defined in that block:They are different, because the value of
i
in both the generator expression and the list comp are evaluated lazily, i.e. when the anonymous functions are invoked inf
.By that time,
i
is bound to the last value ift
, which is -1.So basically, this is what the list comprehension does (likewise for the genexp):
Now the lambdas carry around a closure that references
i
, buti
is bound to -1 in both cases, because that is the last value it was assigned to.If you want to make sure that the lambda receives the current value of
i
, doThis way, you force the evaluation of
i
at the time the closure is created.Edit: There is one difference between generator expressions and list comprehensions: the latter leak the loop variable into the surrounding scope.
The lambda captures variables, not values, hence the code
will always return the value i is currently bound to in the closure. By the time it gets called, this value has been set to -1.
To get what you want, you'll need to capture the actual binding at the time the lambda is created, by: