]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
gh-70870: Clarify dual usage of 'free variable' (#122545)
authorAlyssa Coghlan <ncoghlan@gmail.com>
Tue, 8 Oct 2024 07:52:12 +0000 (17:52 +1000)
committerGitHub <noreply@github.com>
Tue, 8 Oct 2024 07:52:12 +0000 (07:52 +0000)
commit27390990fa9306e2a797a4eb2bd83c5bfc7cb186
treeb103ae76df4d6650724f29645053267d75b4ff95
parentcc9b9bebb2c09c475cb0f278268cce03c115eaea
gh-70870: Clarify dual usage of 'free variable' (#122545)

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".

---------

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]