Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Clarify "late binding" in gotchas#267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
Merged
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletionsdocs/writing/gotchas.rst
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -128,11 +128,12 @@ What Does Happen

Five functions are created, but all of them just multiply ``x`` by 4.

Python's closures are *late binding*. This means that names within closures are
looked up at the time the inner function is *called*.
Python's closures are *late binding*.
This means that the values of variables used in closures are looked
up at the time the inner function is called.

Here, whenever *any* of the returned functions are called, the value of ``i``
is looked up in the surrounding scope at call time, when bythen the loop has
is looked up in the surrounding scope at call time. Bythen, the loop has
completed and ``i`` is left with its final value of 4.

What's particularly nasty about this gotcha is the seemingly prevalent
Expand Down

[8]ページ先頭

©2009-2025 Movatter.jp