-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix ModuleNotFoundError when using pylint_django #7940
Conversation
Ensure that the import path is fixed up before calling ._astroid_module_checker() so that the pylint_django plugin can successfully import the Django settings module when its checkers are initialized.
Pull Request Test Coverage Report for Build 3695649934
π - Coveralls |
π€ According to the primer, this change has no effect on the checked open source code. π€π This comment was generated for commit 1cc95a5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
THanks!
@Pierre-Sassoulas |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the subtle fix @living180 π
@DanielNoord : It's a new cache that is buggy, it started when a dependency change made the python 3.8 env be regenerated I think. This branch is probably using the old cache.
Ensure that the import path is fixed up before calling ._astroid_module_checker() so that the pylint_django plugin can successfully import the Django settings module when its checkers are initialized. Closes #7938 (cherry picked from commit 491eef5) Co-authored-by: Daniel Harding <dharding@living180.net>
Description
Ensure that the import path is fixed up before calling
._astroid_module_checker()
so that thepylint_django
plugin can successfully import the Django settings module when its checkers are initialized.Closes #7938