-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Pylint as a python static code analyzer #298
Conversation
Fix unsuded imports, import order. Renamed entrypoint script plugins.py trying to import "plugins." module causing pylint error.
…o feature/pylint
* Unnecessary use of a comprehension * Unused variables * singleton-comparison * Using built-in python vars * Unnecessary "else" after "raise" * Unnecessary "elif" after "return" * Using deprecated methods
Silence for now, refactor this function in the future. Fix pylint R0914: Too many local variables (23/15) (too-many-locals) See: #327
Silence for now, refactor this function in the future. > R0914: Too many local variables (36/15) (too-many-locals) > R0912: Too many branches (19/12) (too-many-branches) > R0915: Too many statements (104/50) (too-many-statements) See: #328
Silence for now, refactor this function in the future. > R0914: Too many local variables (22/15) (too-many-locals) > R0915: Too many statements (59/50) (too-many-statements) See: #329
The overall cosmetic pylint refactoring is done and pylint check is now succeeding and is part of the CI. However, some parts of the codebase will need more structural rework like extracting some huge functions into classes.
^^ these would be also good first issues/PRs easier to tackle in between the tasks. |
This PR adds Pylint https://pylint.pycqa.org/en/latest/ as a static code analyser for the Python codebase, for quick spotting the common mistakes, errors and enhancing the python coding standards in a minimal automated way.
With #297, closes #271
Quick run: