Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
cad8b0ff
Commit
cad8b0ff
authored
Jan 05, 2013
by
Ezio Melotti
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
#13094: add Programming FAQ entry about the behavior of closures.
parent
d73f369f
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
55 additions
and
0 deletions
+55
-0
Doc/faq/programming.rst
Doc/faq/programming.rst
+52
-0
Misc/NEWS
Misc/NEWS
+3
-0
No files found.
Doc/faq/programming.rst
View file @
cad8b0ff
...
...
@@ -206,6 +206,58 @@ an imported module. This clutter would defeat the usefulness of the ``global``
declaration for identifying side-effects.
Why do lambdas defined in a loop with different values all return the same result?
----------------------------------------------------------------------------------
Assume you use a for loop to define a few different lambdas (or even plain
functions), e.g.::
squares = []
for x in range(5):
squares.append(lambda: x**2)
This gives you a list that contains 5 lambdas that calculate ``x**2``. You
might expect that, when called, they would return, respectively, ``0``, ``1``,
``4``, ``9``, and ``16``. However, when you actually try you will see that
they all return ``16``::
>>> squares[2]()
16
>>> squares[4]()
16
This happens because ``x`` is not local to the lambdas, but is defined in
the outer scope, and it is accessed when the lambda is called --- not when it
is defined. At the end of the loop, the value of ``x`` is ``4``, so all the
functions now return ``4**2``, i.e. ``16``. You can also verify this by
changing the value of ``x`` and see how the results of the lambdas change::
>>> x = 8
>>> squares[2]()
64
In order to avoid this, you need to save the values in variables local to the
lambdas, so that they don't rely on the value of the global ``x``::
squares = []
for x in range(5):
squares.append(lambda n=x: n**2)
Here, ``n=x`` creates a new variable ``n`` local to the lambda and computed
when the lambda is defined so that it has the same value that ``x`` had at
that point in the loop. This means that the value of ``n`` will be ``0``
in the first lambda, ``1`` in the second, ``2`` in the third, and so on.
Therefore each lambda will now return the correct result::
>>> squares[2]()
4
>>> squares[4]()
16
Note that this behaviour is not peculiar to lambdas, but applies to regular
functions too.
How do I share global variables across modules?
------------------------------------------------
...
...
Misc/NEWS
View file @
cad8b0ff
...
...
@@ -867,6 +867,9 @@ Tools/Demos
Documentation
-------------
- Issue #13094: add "Why do lambdas defined in a loop with different values
all return the same result?" programming FAQ.
- Issue #14901: Update portions of the Windows FAQ.
Patch by Ashish Nitin Patil.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment