-
Notifications
You must be signed in to change notification settings - Fork 311
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
mypy disallow-untyped-calls check fails for google-auth 2.30 #1543
Comments
I can reproduce this. I do not see any commit that seems suspicious. When I try to reproduce by pip installing from my filesystem this always fails for me, which makes it difficult to pinpoint any specific regression. How important is this to you? |
It is not that important. We can ignore this mypy check for now, and test if it is resolved in the next google-auth version. It was more out of interest to understand why this error is raised. |
This commit caused issues: c993504 You can reproduce this with:
I guess that something changed in the process of releasing of wheels after 2.29? In 2.29 install from git vs install from pypi gives different results (additional
seems like there was an update:
in f01a690 I would guess that's the reason for github vs pypi installs being different for 2.29 and older (mypy error only for github versions, but no errors for pypi releases), while being the same (mypy error for both pypy and github releases) for 2.30. |
thanks for debugging this further! |
Environment details
google-auth
version: 2.30Steps to reproduce
mypy --ignore-missing-imports --disallow-untyped-calls ./
With google-auth==2.29 this works fine.
With google-auth==2.30 this fails with
error: Call to untyped function "default" in typed context [no-untyped-call]
Did something change from google-auth 2.29 -> 2.30 regarding the typing?
Thanks in advance!
The text was updated successfully, but these errors were encountered: