]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.13] gh-70870: Clarify dual usage of 'free variable' (GH-122545) (#125088)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Tue, 8 Oct 2024 07:58:47 +0000 (09:58 +0200)
committerGitHub <noreply@github.com>
Tue, 8 Oct 2024 07:58:47 +0000 (17:58 +1000)
commit0e0a2dadecae8342782dde5694d1269f248a5473
treea34133813c91fe4ed3d6e7d8717d85a33cbd864a
parente28f2c670541710ecafc0218d025431125d87fc8
[3.13] gh-70870: Clarify dual usage of 'free variable' (GH-122545) (#125088)

The term "free variable" has unfortunately become genuinely
ambiguous over the years (presumably due to the names of
some relevant code object instance attributes).

While we can't eliminate that ambiguity at this late date, we can
at least alert people to the potential ambiguity by describing
both the formal meaning of the term and the common
alternative use as a direct synonym for "closure variable".

---------

(cherry picked from commit 27390990fa9306e2a797a4eb2bd83c5bfc7cb186)

Co-authored-by: Alyssa Coghlan <ncoghlan@gmail.com>
Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
Doc/c-api/code.rst
Doc/glossary.rst
Doc/library/dis.rst
Doc/library/functions.rst
Doc/library/symtable.rst
Doc/library/types.rst
Doc/reference/datamodel.rst
Doc/reference/executionmodel.rst
Misc/NEWS.d/next/Documentation/2024-08-01-17-18-21.gh-issue-70870.fZnBM9.rst [new file with mode: 0644]