Enable Pylint warnings

[kain88-de]

This is a list of good sounding pylint warnings we might want to enable

• arguments-differ,
• assignment-from-none,
• bad-builtin,
• bad-indentation,
• bad-super-call,
• bare-except,
• basestring-builtin,
• broad-except,
• deprecated-lambda,
• expression-not-assigned,
• filter-builtin-not-iterating,
• function-redefined,
• indexing-exception,
• map-builtin-not-iterating, Enable more pylint warnings #1302
• next-method-called,
• no-absolute-import, Lint absolut import #1294
• old-division, Always use new division #1293
• print-statement, Enable more pylint warnings #1302
• property-on-old-class,
• range-builtin-not-iterating, Enable more pylint warnings #1302
• redefined-builtin,
• redefined-outer-name,
• reduce-builtin,
• reimported,
• relative-import, Lint absolut import #1294
• round-builtin,
• super-init-not-called,
• unnecessary-lambda,
• unnecessary-semicolon,
• unpacking-non-sequence,
• unused-argument,
• unused-import, Enable Pylint warning unused-import #4518
• unused-variable,
• unused-wildcard-import,
• used-before-assignment,
• wildcard-import,
• xrange-builtin, Enable more pylint warnings #1302
• zip-builtin-not-iterating, Enable more pylint warnings #1302

[orbeckst]

We have been linting for a while. Can we close this issue?

[kain88-de]

we haven't enabled all of them. For example I would like to enable unused import or bad super call to find more code pieces that could need work. I never found the time. This is a good issue for hacktober fest. Just enable a single lint option and fix all the warnings. We can have a PR for every option enabled.

Not all will make sense though. unused argument could cause trouble because our API doesn't use all variables for all sub-classes.

[orbeckst]

Then we keep this issue open as a master issue and create new ones for individual linter warnings, similar to what we've been doing with testing of exceptions.

[aditi2906]

@orbeckst @kain88-de I am willing to initiate work on this issue. I wanted to know if we can configure the prospector tool under this issue since we can get to manipulate the strictness?

[orbeckst]

What is the "prospector tool"? Can you elaborate? Explain what you want to do, include links as relevant.

[kumarvaastavi]

Are the warnings unused import and unused variable still open, can I work on them?

[orbeckst]

Are the warnings unused import and unused variable still open, can I work on them?

I think so. Create a PR, enable the warnings, and then start fixing them. When you open your PR, mention this issue (#1295) in the description so that we see it here. In general we don't "reserve" work but simply look at the first PR that comes in. Nevertheless, communicating with each other is good (like you did), especially when coming new into a project.

Note that there's a closed PR #4111 where someone else attempted work — I'd suggest to also look at that PR to learn from it.

[kumarvaastavi]

I will try fixing them and open PR as you said