-
Notifications
You must be signed in to change notification settings - Fork 964
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
Module Import Errors #193
Comments
Sorry for not getting back to you! I've had a busy couple of months. I would prefer not to try to "trick" the import system by import modules instead of module members. I think people should be free to use whichever makes the most sense at the time. As to the exact issue here, PR #206 will solve that particular circular import and that's how I'd prefer to handle this going into the future, by fixing the circular imports where they happen. |
Fix #193 by basing path off of warehouse not warehouse.application
Numerous modules raise import errors.
Example:
Should Warehouse import modules instead of module members? Importing modules might help avoid resolving classes & functions at import-time, and raising import errors like in this circular import example.
The text was updated successfully, but these errors were encountered: