Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Use "caller" instead of "global" to describe where imports go #953
Conversation
|
@apjanke I don't like the word caller because you don't call a module in the sense of calling a function or class method. What about saying "the local namespace" instead? That matches the terminology used in the official Python docs. |
apjanke
force-pushed the
apjanke:global-vs-caller-namespace
branch
from
345999f
to
d012a66
|
Yes, that makes sense. I've updated this PR to do that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
This passage talks about
importcopying names into the global namespace. But doesn't it copy names into the calling module's namespace instead?