Taking Python beyond scripting
summary
Argues that shipping Python as a product needs tool chains not just scripts: recommends static analysis (use Ruff (Rust backed, ~800 rules, auto‑fix) alongside Pylint/Flake8), type checking (mypy, Pyright, pytype, Pyre), formatters (Black/isort) and git hooks (pre‑commit + Ruff auto‑format prevents bad commits). Shows using UV for project init, pinned lockfiles with hashes, and adding linters/types as development deps. Demo commits fail until docstrings and format issues are fixed, proving the workflow enforces quality.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 6:38Python’s flexibility
- 11:38Static analysis matters
- 24:32Type validation in Python
- 33:54Code formatting standards
- 37:23Demo: UV setup and linting
- 46:07Q&A
related talks
41mEcosystem for Reliable Python Programming
21mTeach Your Old Code New Tricks: Automating Code Quality in Large Projects
22mPublishing well formed Python packages
34mSecure Python Development: Tips, Tricks, and Tools
27mAn Overview of the Python Code Tool Landscape 2023
24mPython for Humans, Designing Python Code Like a User Interface
29mCode Quality in Python - tools and reasons
30mPython Tricks You Can't Live Without