-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Inconsistent results after 0.960 -> 0.971 migration #13422
Comments
Sorry, but I cannot find a reproducer. |
Can you check if it is fixed with mypy master? |
I will take a look! |
Oh the other thing is if you have editable installs in CI, make sure you're using setuptools < 64. New setuptools breaks all IDE and static analysis tools. They knew of the issue and did it anyway 🤷 |
🤦 |
Any upstream discussions about this? |
pypa/setuptools#3518 (and https://mail.python.org/archives/list/[email protected]/thread/IIVBPYDZR5T5BGPAWFVYS5ZPYDXGVHQN/#OSWHT5VSRGKPSPYD7PQWR2M4OCSL5WO3) |
Is there anything actionable in this bug report? Was there a repro identified? Did it turn out to be a problem with editable installs? |
I am trying to migrate our huge code base from mypy 0.960 to 0.971, but odd things are happening.
For example, our CI fails with:
Link: https://github.com/typeddjango/django-stubs/runs/7838309248?check_suite_focus=true
Locally it works as expected (python and mypy versions do match):
Since we have quite a complex structure, it might be something on our side.
So, what do we do?
We store all stubs for django in
django-stubs
folder.At the same level we have
mypy_django_plugin
that does fancy stuff with ORM / etc.Our plugin imports a lot of things from django itself (settings,
.setup()
, etc).Here's the tricky part: 0.960 recognised these imports and their types.
Right now my local setup with 0.971 does the same thing.
But, 0.971 in our CI does not see our stubs. So, all types are just
Any
s. This is unexpected!Link: https://github.com/typeddjango/django-stubs
Original PR: typeddjango/django-stubs#1108
The text was updated successfully, but these errors were encountered: