Unpopular Opinion? - Python Typing Is Not Worth It
summary
Demonstrates that Python type annotations do not enforce runtime checks and require external tools like mypy to catch mismatches, argues that autocompletion and AI reduce the writer benefit, and cites a large, mostly untyped production project with 1.5 million downloads that works fine without types. Notes a near-successful Python 4 mandatory typing proposal and references the Flask creator’s blog saying typing didn’t pay dividends, framing typing as a tradeoff, not a requirement.
AI-written summary · about
chapters (11)
- 0:00Introduction: Criticism of Python Typing
- 0:12Adding Types in Python: Expectations vs Reality
- 0:29Python Doesn't Enforce Types by Default
- 0:51The Role of mypy and Static Type Checkers
- 1:06Types for Readers or Writers?
- 1:30Autocompletion, AI, and Developer Experience
- 1:58Real-World Large Untyped Python Project
- 2:28Push for Mandatory Typing in Python 4
- 3:10Tradeoffs and Community Perspectives
- 3:40Final Thoughts: Freedom to Choose
- 4:00Outro: Happy Coding
related talks
57mWhy You Should Care About Types
28mMind the gap! Why static typing requires more than just adding annotations
32mStatic Typing in Python
22mStatic Typing in Python
24mStatic type-checking is dead, long live static type-checking in Python!
24mDuck Typing Is For The Birds
35mStatic Typing in Python
13mPython 3 Types in the Wild: A Tale of Two Type Systems