Automatic Checks for the People

twitter: @MislavCimpersak
github: github.com/mislavcimpersak

- Fast forward few years and I'm doing Python. - Life is good. - We have PEP8. - So I'm using it. - My other team members are not. - And they are not wrong. - Sometimes it produces code that is even less readable. - Then, all of a sudden we also have PyChecker, PyLint, PyFlakes... - So many possible rules can be set and even when they are set in some guide book in some wiki or a readme, they are hard to enforce. - And let me tell you: - If they are not enforced automatically, they are not happening. - Enter the first line of defense:

Pre-commit

Code formatting

PEP 8

aka.

pycodestyle

github.com/PyCQA/pycodestyle

YAPF

github.com/google/yapf

github.com/psf/black

Valid code

valid Python
valid bash script
valid Ruby
buildable Go
...

Valid code

docstring existance
debug statements
merge conflict strings
trailing whitespace
end of file whitespace
...

Valid code

valid JSON
valid YAML
valid TOML
valid XML
...

Imports sorting

Dependencies sorting

CI

Coverage decrease

Prospector

github.com/PyCQA/prospector

PyLint, PyFlakes, pydocstyle, McCabe, Dodgy...

Bandit

github.com/PyCQA/bandit

MyPy

github.com/python/mypy

Docker linter

github.com/hadolint/hadolint

Terraform

Where to start?

Formatting

Formatting

One commit

Formatting

Boy scout rule

Checks

Down the line

joind.in/talk/1c349

mislavcimpersak.github.io/automatic-checks-for-the-people-talk