implement pylint
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
As we recently faced few costly bugs that could have being easily prevented by a simple run of pylint, we should assure we include pylint in the list of linters run on our code.
Once first repository that got it introduced is tripleo-common and introduction is supposed to be gradual: fixing a small number of issues per patch, backporting it to supported branches and continuing with addressing other temporary disabled checks.
That process is expected to take a longer period of time, especially due to the need to backport these.
The main reason for backporting is that by doing it we make it easier to backport other patches. While nobody forces us to backport these changes, doing it will payoff quickly on other changes that will no longer create conflicts when we cherry-pick them for backporting.
| Sorin Sbarnea (ssbarnea) wrote | #1 |
The first patch that introduced pylint can be seen at https:/