[pylint] prepping for enabling pylint for non-errors #4884
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To help improve stability, consistency, and code quality I thought it would be prudent to enable
pylint
for non-errors. Given that numbers of (C)onvention, (R)efactor, and (W)arning violations it seemed best to first i) enable the checks intox.ini
and, ii) disable the checks on a per file basis, to make the problem more tractable.My plan is to systematically go through these files one-by-one in a series of digestable PRs to remedy the issues.