Skip to content

Use "caller" instead of "global" to describe where imports go #953

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 1 commit into from
Dec 28, 2018
Merged

Use "caller" instead of "global" to describe where imports go #953

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 docs/writing/structure.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -441,8 +441,8 @@ bad practice. **Using** ``import *`` **makes code harder to read and makes
dependencies less compartmentalized**.

Using ``from modu import func`` is a way to pinpoint the function you want to
import and put it in the global namespace. While much less harmful than ``import
*`` because it shows explicitly what is imported in the global namespace, its
import and put it in the local namespace. While much less harmful than ``import
*`` because it shows explicitly what is imported in the local namespace, its
only advantage over a simpler ``import modu`` is that it will save a little
typing.

Expand Down