Skip to content

gh-61585: Clarify import scope in modules tutorial #93455

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
merged 4 commits into from
Jun 28, 2022
Merged

gh-61585: Clarify import scope in modules tutorial #93455

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d77be8f
Clarify import scope in modules tutorial
slateny Jun 3, 2022
52ac1f8
Use namespace instead of symbol table
slateny Jun 12, 2022
91ffb42
Change all instances of symbol table to namespace
slateny Jun 15, 2022
c37485f
Change 'enters' to 'adds'
slateny Jun 15, 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
4 changes: 2 additions & 2 deletions Doc/tutorial/modules.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,8 +84,8 @@ refer to its functions, ``modname.itemname``.

Modules can import other modules. It is customary but not required to place all
:keyword:`import` statements at the beginning of a module (or script, for that
matter). The imported module names are placed in the importing module's global
symbol table.
matter). The imported module names, if placed at the beginning of a module,
are placed in the importing module's global symbol table.

There is a variant of the :keyword:`import` statement that imports names from a
module directly into the importing module's symbol table. For example::
Expand Down