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.

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

merged 1 commit into from
Dec 28, 2018

Conversation

apjanke
Copy link
Contributor

@apjanke apjanke commented Dec 17, 2018

This passage talks about import copying names into the global namespace. But doesn't it copy names into the calling module's namespace instead?

@mpoulin
Copy link
Contributor

mpoulin commented Dec 27, 2018

@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
Copy link
Contributor Author

apjanke commented Dec 27, 2018

Yes, that makes sense.

I've updated this PR to do that.

@mpoulin mpoulin merged commit 979b4cd into realpython:master Dec 28, 2018
@apjanke apjanke deleted the global-vs-caller-namespace branch December 28, 2018 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants