-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add an faq detailing which messages to disable to avoid duplicates w/ other popular linters #3647
Conversation
1 similar comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the work, this is useful. I think maybe mccabes and too many branches are not exactly the same ? I also think it would makes default configuration or automatic disabling discussed in #3512 a lot easier to implements.
You would be correct that mccabe and too-many-branches are not exactly the same but they are fairly close. The too-many-branches just puts an upper bound on the branches which is simpler than what mccabe does which is measure the cyclomatic complexity (which main factor is number of branches but then assigns it a score). So while not exactly the same, mccabe is essentially a more complex version. I would think if you had mccabe enabled, too-many-branches is not going to give you any extra intelligent information. |
mixed-indentation, bad-whitespace, and bad-continuation have been removed in the upcoming release of pylint
Fair enough :) |
Description
Add an FAQ detailing which messages to disable to avoid duplicates when using other popular linters alongside pylint. Includes pycodestyle, pyflakes, mccabe, pep8-naming, and flake8-import-order.
Type of Changes
Related Issue
Related: #3512, #3517
This does not resolve them in any way. It only adds instructions in the faq on how to configure pylint manually while using other linters