This document provides a tour of various Python static analysis tools, including PEP8 for style guidelines, PyFlakes for unused names, Pyroma for checking setup.py files, PEP257 for docstring standards, Vulture for unused code, Pylint for code quality and standards, complexity metrics like McCabe and Halstead, maintainability index, Dodgy for security issues, Bandit also for security, Flake8 which wraps other tools, Prospector which runs multiple tools, and pre-commit for running checks before commit. It aims to help users choose the right tools to improve code quality, style, and health.

1. STATIC ANAYLSIS
A TOUR OF PYTHON TOOLS
Created by Jason A Myers / @jasonamyers

2. STATIC ANALYSIS

4. PEP8

5. PYFLAKES
Names which are used but not defined or used before
they are defined
Names which are redefined without having been used

6. PYROMA
Checks setup.py files for errors and issues

7. PEP257
Checks that docstrings match PEP257 standards

9. VULTURE
Checks for unused code

10. PYLINT
Looks at your project as a whole and reports back very
detailed information on Code Standards, ineffecient code,
errored implementation code, and duplicate code

11. COMPLEXITY
Imperfect science

12. MCCABE/CYCLOMATIC COMPLEXITY
Focuses on decisions made in software

13. HALSTEAD COMPLEXITY
Focuses on Volume, Difficulty, and Effort

15. MAINTAINABILITY INDEX
Focuses on ease to support and change

16. MCCABE

17. RADON

19. DODGY

20. BANDIT

21. FLAKE8
Flake8 is a wrapper around these tools: PyFlakes, pep8, and
McCabe.

22. PROSPECTOR
RUN ALL THE THINGS!
Combines: PyLint, PEP8, pyflakes, McCabe, dodgy, and
PEP257
Optionally: Pyroma and Vulture

23. PRE-COMMIT
Runs before if lets you create a commit on your machine

24. QUESTIONS?