Pylint does not play very well with dynamic object
manipulation in python This creates a lot of
false-positives in the code-base which affects
contributors looking for genuine failures.
So, this change
- adds pylint ignore statements where appropriate
to disable testing these lines of code and failing.
- replaces all the pylint error codes (they are
hard to remember/relate to) with error names
which are easier to understand when reading the
code.
- initializes sqlalchemy model objects as dictionaries
which is a valid representation over None.
- removes ignore directives on six.moves which
is globally ignored in our pylintrc.
- adds alembic.op to the ignored
modules list since they are not supported by
pylint and have known issues.
This patch is the beginning of a series of
commits to use pylint in a sane way on manila code.
Change-Id: I44616821c5311d6f14986697efbbe5624de364a5
This commit does several things:
- Setup and run pylint directly rather than running through a script.
This allows the user to see what is happening while the user is running
through pylint.
- Allow the user to either run pylint on a particular changeset,
or the entire manila tree.
- Allow the user to run on a particular changeset. Using like HEAD~1,
etc.
- I disabled the tests that were reported by pylint.
The thought here would be go through the failures
and correct them.
- Update pylint to 2.1.1.
Change-Id: I398d1ba01a3fd7f1c86ad4065a7984d276f33383
Signed-off-by: Chuck Short <chucks@redhat.com>