-
-
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
More "syntax error in type comment"s #9916
Comments
Expected on 0.740, but was fixed well before 0.790 (and I can't repro). Feel free to re-open if you can't get it to work, but closing since I'm quite sure you're still using an old mypy (maybe try |
Hm, yes, in spite of installing a fresh copy in a venv, it seems there was an issue with which mypy was used. Thank you. |
I'm trying to use mypy 0.812 with python 3.9.4 on Arch but am seeing these:
I'm also using venv if that makes a difference? EDIT: My fault - fixed by updating the version of mypy being called via pre-commit. |
For those who have gotten this after an upgrade to Python 3.9, I was able to get things fixed with |
I generally would recommend running the latest mypy unless something is holding you back. |
In an ideal world yup, but unfortunately because of the breaking changes that get introduced in new versions of mypy, the amount of effort required to upgrade something is |
* regarding typed-ast see: python/typed_ast#159 (comment) * regarding mypy see: python/mypy#9916 * further: ignore "error: Unpacking a string is disallowed" -> credentials may also be a string... Change-Id: I57daada9f8340075bf92be308310ec341a3f3d5d
Bug Report
Related to #8627
To Reproduce
Expected Behavior
No issues
Actual Behavior
Unable to effectively sort through messages because of the ~360 from this module alone
Your Environment
mypy.ini
(and other config files): noneThe text was updated successfully, but these errors were encountered: