Skip to content

gh-70393: Clarify mention of "middle" scope #98839

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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Merged
JelleZijlstra merged 2 commits into from
Dec 12, 2022
Merged

gh-70393: Clarify mention of "middle" scope #98839

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bfbad0c
gh-70393: Clarify mention of "middle" scope
hauntsaninja Oct 29, 2022
c498ae0
grammar fix
JelleZijlstra Nov 2, 2022
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
Next Next commit
gh-70393: Clarify mention of "middle" scope
  • Loading branch information
@hauntsaninja
hauntsaninja committed Oct 29, 2022
commit bfbad0c73263c279d5834ecf1ad007dc03dc03c6
2 changes: 1 addition & 1 deletion Doc/tutorial/classes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ directly accessible:
* the outermost scope (searched last) is the namespace containing built-in names

If a name is declared global, then all references and assignments go directly to
the middle scope containing the module's global names. To rebind variables
the next-to-last scope containing the module's global names. To rebind variables
found outside of the innermost scope, the :keyword:`nonlocal` statement can be
used; if not declared nonlocal, those variables are read-only (an attempt to
write to such a variable will simply create a *new* local variable in the
Expand Down