Skip to content
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

globals and Settings interfere with "import mypackage.*" #30

Open
apjanke opened this issue Sep 12, 2021 · 0 comments
Open

globals and Settings interfere with "import mypackage.*" #30

apjanke opened this issue Sep 12, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request thinkers Things we have to think about

Comments

@apjanke
Copy link
Member

apjanke commented Sep 12, 2021

Because globals and Settings are generically named, you can't do an import mypackage.* without likely getting collisions. Maybe we should do something about this? Move them to a subpackage?

Or maybe it's better design if we leave packages to provide their own subpackages specifically designed for import * operations?

@apjanke apjanke self-assigned this Sep 12, 2021
@apjanke apjanke added enhancement New feature or request thinkers Things we have to think about labels Sep 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request thinkers Things we have to think about
Projects
None yet
Development

No branches or pull requests

1 participant