Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Eliminate broad-except suppression | 2018-04-19 | |
| | |||
* | Eliminate bare-except suppression | 2018-04-19 | |
| | |||
* | Eliminate old-style-class suppression | 2018-04-19 | |
| | |||
* | Eliminate wildcard-import suppression | 2018-04-19 | |
| | |||
* | Eliminate function-redefined suppression | 2018-04-19 | |
| | |||
* | Eliminate unnecessary-lambda suppression | 2018-04-19 | |
| | |||
* | Eliminate undefined-variable suppression | 2018-04-19 | |
| | |||
* | Eliminate non-iterator-returned suppression | 2018-04-19 | |
| | |||
* | Eliminate undefined-loop-variable suppression | 2018-04-19 | |
| | |||
* | Eliminate raising-bad-type suppression | 2018-04-19 | |
| | |||
* | Eliminate unreachable suppression | 2018-04-19 | |
| | |||
* | Eliminate bad-continuation suppression | 2018-04-19 | |
| | |||
* | Run pylint on Python test code | 2018-04-18 | |
The test modules were not under pylint jurisdiction, and actual bugs have been found in tests that would have been prevented had we run static analysis on the test code as we do on the core modules. This is the first step to enable pylint on tests. Due to numerous warnings since the code is not ready and needs refactoring, a new `.pylintrc` specific to tests is added that suppresses a number of valid warnings. The goal is stepwise elimination of each class of warning while refactoring the code such that it will not emit any warnings in future commits, always keeping the sanity checks passing and keeping the disruption minimal. |