Static Type Analysis for Robust Data Products
summary
Shows actual adoption steps: use the typing module (Python 3.5+) to annotate functions, run mypy on CI, catch concrete errors like “incompatible return value type” when a function declared to return dict actually returns list, and rely on caching so checks stay fast. Embraces gradual typing using the any placeholder for third‑party code or iteratively refined stubs, and documents when to add stubs, wire checks into build scripts, and balance duck typing with type safety.
AI-written summary · about
chapters (10)
- 0:00Static typing in Python
- 10:38Robust data product challenges
- 12:25Static typing benefits
- 13:52Python type hints & mypy
- 18:31Mypy in development
- 21:45Static typing vs duck typing
- 22:30Static typing for mature products
- 26:29Python static typing future
- 27:45IDE support for typing
- 29:59Q&A on typing tools
related talks
32mStatic Typing in Python
29mStatic Typing in Python
30mStatic type checking with mypy
35mStatic Typing in Python
22mStatic Typing in Python
32mType-checked Python in the real world
28mMind the gap! Why static typing requires more than just adding annotations
38mMigrating existing codebases to using type annotations