-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
mypy is failing on the stdlib #7019
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
Comments
This is the line on which mypy is reporting the error: typeshed/stdlib/email/message.pyi Line 13 in 35064a7
But I have no idea why, as aliasing |
Weird, from diffing CI runs, change of Python version from 3.10.1 to 3.10.2, maybe? |
But it's also failing on 3.8! |
That's just the version that's being passed to mypy. In all cases, mypy is running on Python 3.10. I'm guessing there could be an |
Ah, gotcha. |
A hack that might fix python#7019
So weird. Thanks both for getting things green. I'd also welcome any hypotheses :-) |
CI is currently failing on all PRs with the following message from mypy:
stdlib/email/message.pyi:13: error: Cannot determine type of "Any" [has-type]
.E.g.:
TODO
to supportConcatenate
incurses
#7018mypy appears to be failing on all platforms, but only on Python 3.8+.
I can also reproduce this error locally. No idea what's changed to make it suddenly start erroring as part of the CI checks, though.
The text was updated successfully, but these errors were encountered: