Preventing headaches with linters and automated checks
summary
Claims linters do more than PEP8: they consolidate executable knowledge so framework quirks become automated checks. Demonstrated tools include Django System check framework, flake8/pyflakes, pylint with astroid-powered inference, bandit and safety; pre-commit hooks and CI enforce them. Built examples actually work: a custom system check rejects non-callable ArrayField defaults and an AST/astroid rule finds missing returns after queryset calls. Dozens of linters exist and the demos run successfully.
AI-written summary · about
chapters (11)
- 0:00Intro
- 3:16Common linter mistakes
- 4:06Can linters prevent bad patterns
- 6:31System checks
- 8:07Dynamic analysis
- 8:57Dynamic checks
- 10:55Static analysis
- 18:18New linter
- 19:18Asteroid
- 21:36MyPI
- 23:00When to run
related talks
27mPython Linters at Scale
20mHidden Hacks in Linters for Better & More Secure Code
30mAutomating Code Quality
05mTool Confusion: Pythonic Code with flake8, tox and pre-commit
19mMake Linting Great Again
21mTeach Your Old Code New Tricks: Automating Code Quality in Large Projects
29mCustom Source Code Checks
31mHow GitHub uses linters