-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Mistype of empty tuples #4090
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
I think this is an old issue, #224. Your description makes it sound like this is a regression in 0.530 though, can you confirm that? If so, this should be high priority to fix. |
This was not getting caught by our CI with |
I tried to bisect this and found it still occurs back with version 0.501, so don't think this is a regression. Probably there was some other reason why the real code that you were checking passed (perhaps some other bug make mypy ignore some code). FWIW the example I tried was: a = () + (1,2) This gives two errors:
|
Since this is not a regression, I propose to close this as a duplicate of #224 |
Perhaps I'm missing some subtlety here but mypy complains about two usages for empty tuples that I do not believe are invalid:
This gives:
Typing this out, it feels like it might be an issue with generics. This started getting reported in 0.530 for me.
The text was updated successfully, but these errors were encountered: