-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
useless-type-doc conflicts with mypy no-untyped-def, unsure how to proceed #4117
Comments
Hello, thank you for opening the issue. Do you have a code example so I can understand the problem better ? (You can disable the pylint message with |
Sample:
I have the following settings: mypy.ini :
However, when I change the test() function definition line to
I'm guessing these two settings
|
I'm still hitting this in pylint 2.8.3 and astroid 2.5.6 (I have ignore lines though). I've updated my settings file above, as I had regrettably missed this part out:
@Pierre-Sassoulas do you mind testing to see if you can reproduce this? |
I had some time to look at this, I think this is a false positive in pylint, Another issue for this is #4593 |
With pylint 2.7.0, we now have the
useless-type-doc check.
I also havedisallow_untyped_defs = True
turned on for mypy.I have some functions with unused variables that I append a
_
to the name, e.g._name
and set a type to them. pylint 2.7.0 now throwsuseless-type-doc
error, and when I remove the type, mypy throws theno-untyped-def
error.What's the best way forward? Should I change the mypy config, or should I ignore this pylint error?
This worked with pylint 2.6.x, since it does not have the
useless-type-doc
check.The text was updated successfully, but these errors were encountered: