-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Upgrading 4.3.2
-> 4.4.1
causes mypy type checking to fail
#2186
Comments
It's probably a mypy related question, but rather bring it up here, as this whole mypy "which modules to ignore and how" is pretty confusing (seemingly to many). I've tried to add both below to the [mypy-troposhpere.*]
ignore_missing_imports = True
[mypy-troposhpere]
ignore_missing_imports = True Still getting Putting it to the top level makes running mypy ignore the issue, but that's not ideal as it affects other packages as well: [mypy]
ignore_missing_imports = True This results in (It's another issue though that with this setting I'm still getting I'd really appreciate any recommendations how to get this working properly, I've spent at least an hour with this specifically because of troposphere. |
@g-borgulya I was able to reproduce with your example. I believe the issue was the spelling of "troposphere" in the section names. Here's my results correcting that issue.
Let me know if this works for you. I do need to create a tracking issue and branch to get better typing support implemented. |
I so much appreciate it, @markpeek ! Thank you. Yes, mypy works with the fixed settings. |
Hi,
to keep it short, when upgraded
4.3.2
->4.4.1
, mypy started throwing following errorsmypy config is
Pydantic version is
"==1.10.12"
Mypy version is
mypy = "1.5.1"
Please let me know if more information is needed.
The text was updated successfully, but these errors were encountered: