Tool Confusion: Pythonic Code with flake8, tox and pre-commit
summary
Project enforces linters by running pre-commit as the canonical runner, invoked from tox and executed in CI via tox-gh-actions, so linters share one pinned version and config instead of ad hoc IDE, system or per-developer installs. flake8 rules live in the pre-commit hook, tox runs pre-commit run --all-files in a Python 3.9 env, and GitHub Actions runs tox; this prevents bad commits, speeds feedback, and is already used in repositories like Flask-reuploaded and hibpcli.
AI-written summary · about
related talks
30mAutomating Code Quality
21mTeach Your Old Code New Tricks: Automating Code Quality in Large Projects
28mPreventing headaches with linters and automated checks
36mContinuous Integration For The Win!
27mPython Linters at Scale
30mLearn how to never commit $%@ to Git
29mCustom Source Code Checks
08mAutomated Checks Before Publishing Open Source, a Few Years La...