make lint: use config file and plugin for pylint

Our custom implementation of pylint checker is often broken by
incompatible change on pylint side. Using supported solutions (config
file, pylint plugins) should avoid this issue.

The plugin adds missing (dynamic) member to classes in abstract syntax
tree generated for pylint, instead of just ignoring missing members and
all sub-members. This should improve pylint detection of typos and
missing members in api. env and test config.

make-lint python script has been removed, to run pylint execute 'make
lint'

https://fedorahosted.org/freeipa/ticket/5615

Reviewed-By: David Kupka <dkupka@redhat.com>
Reviewed-By: Jan Cholasta <jcholast@redhat.com>

1 files changed, 85 insertions, 0 deletions

diff --git a/pylintrc b/pylintrc
new file mode 100644
index 000000000..29db1049c
--- /dev/null
+++ b/pylintrc
@@ -0,0 +1,85 @@
+[MASTER]
+# Pickle collected data for later comparisons.
+persistent=no
+
+# List of plugins (as comma separated values of python modules names) to load,
+# usually to register additional checkers.
+load-plugins=pylint_plugins
+
+# Use multiple processes to speed up Pylint.
+jobs=1
+
+[MESSAGES CONTROL]
+
+enable=
+    all,
+    python3
+
+disable=
+    R,
+    I,
+    invalid-name,
+    import-error,
+    abstract-method,
+    anomalous-backslash-in-string,
+    arguments-differ,
+    attribute-defined-outside-init,
+    bad-builtin,
+    bad-indentation,
+    bare-except,
+    broad-except,
+    dangerous-default-value,
+    eval-used,
+    exec-used,
+    fixme,
+    global-statement,
+    global-variable-not-assigned,
+    global-variable-undefined,
+    no-init,
+    pointless-except,
+    pointless-statement,
+    pointless-string-statement,
+    protected-access,
+    redefine-in-handler,
+    redefined-builtin,
+    redefined-outer-name,
+    reimported,
+    relative-import,
+    super-init-not-called,
+    undefined-loop-variable,
+    unnecessary-lambda,
+    unnecessary-semicolon,
+    unused-argument,
+    unused-variable,
+    useless-else-on-loop,
+    bad-classmethod-argument,
+    bad-continuation,
+    bad-mcs-classmethod-argument,
+    bad-mcs-method-argument,
+    bad-whitespace,
+    blacklisted-name,
+    invalid-name,
+    line-too-long,
+    missing-docstring,
+    multiple-imports,
+    multiple-statements,
+    old-style-class,
+    superfluous-parens,
+    too-many-lines,
+    unidiomatic-typecheck,
+    no-absolute-import
+
+
+[REPORTS]
+
+# Set the output format. Available formats are text, parseable, colorized, msvs
+# (visual studio) and html. You can also give a reporter class, eg
+# mypackage.mymodule.MyReporterClass.
+output-format=colorized
+
+# Tells whether to display a full report or only the messages
+reports=no
+
+# Template used to display messages. This is a python new-style format string
+# used to format the message information. See doc for all details
+msg-template='{path}:{line}: [{msg_id}({symbol}), {obj}] {msg})'