-
Notifications
You must be signed in to change notification settings - Fork 23
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
Revisit disabled-by-default errors #86
Comments
This was referenced Jan 16, 2022
Merged
JelleZijlstra
added a commit
to JelleZijlstra/typeshed
that referenced
this issue
Jan 16, 2022
Unblocks turning on Y092; see PyCQA/flake8-pyi#86
Y090 and 91 are gone now. Y092 has significant false positives and limited upside (python/typeshed#6930), so I'm proposing to remove it in #88. That leaves only Y093, about using TypeAlias. I suggest we simply turn that on by default now and turn it off in typeshed until all type checkers support it. That way, we can get rid of the fragile handling for disabled-by-default errors in this plugin. |
AlexWaygood
pushed a commit
that referenced
this issue
Jan 19, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'd like to get rid of the disabled-by-default Y090, Y091, and Y092. This will require a couple of different changes both in typeshed and here, so I'm opening this issue to track them all.
Y090 and Y091
These are essentially special cases of Y010 (don't put stuff in a function body) that we disabled for compatibility years ago. There are no remaining triggers for these rules in typeshed, so I propose that we get rid of the separate codes and make Y010 trigger on everything you may put in a function body.
Y092 triggers on a lot of existing typeshed code:
These are mostly of the form
constant: type = ...
, and they seem legitimate to me. I'll send a PR to typeshed to get rid of the= ...
. After that we can consider turning it on by default.The text was updated successfully, but these errors were encountered: