-
-
Notifications
You must be signed in to change notification settings - Fork 462
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
KeyError: 'django.conf.global_settings' #48
Comments
I'm also getting this error on Python 3.6.5 with
But uninstalling @Naddiseo can you check if this workaround works for you too? |
@ncvc This means that my monkeypatches aren't going to work anymore after python/mypy#6588 lands... |
What does django-stubs need in order to not need to monkeypatch any mypy internals? We can arrange to have the right hooks, within reason. |
There are two: It forces mypy to load modules which never appear in the import graph: Probable workaround: ask users to seed from those places explicitly, and fallback to Hook: allow plugin to specify additional modules to seed mypy type checking. python/mypy#5911 Django stores project settings in special
Problem here is that I've added user settings modules as a dependency for Probable workaround: add catch-all |
It seems to me that 1 isn't necessarily needed and should fall out of adding the dependencies (at least, if the dependencies are to stubs, which are always follow=normal?). With that in mind, it seems like it should be sufficient to add a hook that allows a plugin to add additional dependencies to a module? |
So, I will be able to express "make a |
Yeah |
Is this still relevant or can be closed in view of python/mypy#6598 being already merged? |
It's going to be relevant when 0.700 will be out, should be closed after a merge of this one https://github.com/mkurnikov/django-stubs/pull/60. Current |
Not sure where to report this, or even how to debug it, but I've been receiving the following error for the past few days that seems to be coming from django-stubs:
Unfortunately, our codebase is too big to reduce to a test case, but I can do local debugging if you let me know what/where to look.
The text was updated successfully, but these errors were encountered: