Title: An error in bindings of closures
Type: behavior Stage:
Components: None Versions: Python 2.7
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: Frederick.Ross, amaury.forgeotdarc
Priority: normal Keywords:

Created on 2012-05-23 16:19 by Frederick.Ross, last changed 2012-05-23 18:52 by amaury.forgeotdarc. This issue is now closed.

Messages (4)
msg161432 - (view) Author: Frederick Ross (Frederick.Ross) Date: 2012-05-23 16:19
The following code throws an UnboundLocal error:

def f(x):
    def g():
        x = x + "a"
        return x
    return g()
msg161437 - (view) Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) * (Python committer) Date: 2012-05-23 16:34
This is expected behavior:
msg161442 - (view) Author: Frederick Ross (Frederick.Ross) Date: 2012-05-23 17:49
Assignment in Python creates a new binding. Whether the new binding shadows or replaces an old binding should be irrelevant. This behavior is inconsistent with that. Please fix expectations, and then Python interpreter.
msg161449 - (view) Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) * (Python committer) Date: 2012-05-23 18:52
What fails here is the evaluation of "x", not the assignment!

You are right concerning the assignment, the outer definition has no effect at all.  The very presence of "x = " in the function code turns x into a local variable for the whole function; so 'x + "a"' fails because the local variable has not value yet.

Python, unlike Lisp, defines scopes lexically, not dynamically. There is no "previous" binding, but "local" or "outer" scopes.
Date User Action Args
2012-05-23 18:52:29amaury.forgeotdarcsetstatus: open -> closed
resolution: not a bug
messages: + msg161449
2012-05-23 17:49:01Frederick.Rosssetstatus: closed -> open
resolution: not a bug -> (no value)
messages: + msg161442
2012-05-23 16:34:51amaury.forgeotdarcsetstatus: open -> closed

nosy: + amaury.forgeotdarc
messages: + msg161437

resolution: not a bug
2012-05-23 16:19:36Frederick.Rosscreate