Talk Python To Me #539: Catching up with the Python Typing Council
10 snips
Mar 6, 2026 Carl Meyer, a Rust-based type checker developer with experience adding typing at Instagram. Rebecca Chen, a Python typing engineer who worked on Google’s Python team. Jelle Zijlstra, a typing council member focused on language governance at OpenAI. They explore how the typing council governs spec decisions, clashes between type checkers, new Rust-based checkers, nullability debates, and practical guidance on how much typing to add.
AI Snips
Chapters
Transcript
Episode notes
Typing Council Created For Fast Practical Decisions
- The Python Typing Council exists to make incremental, practical typing-spec decisions without the full PEP process.
- Jelle Zijlstra explained it lets type-checker authors and users agree on small but important behavior changes quickly.
Unified Typing Spec Reduces Fragmentation
- typing.python.org consolidates PEPs into a single evolving typing specification to reduce fragmentation.
- Jelle Zijlstra rewrote the TypedDict section to combine multiple PEPs into coherent docs for clarity.
Numeric Type Semantics Are Contentious
- The meaning of numeric annotations (e.g., float vs int) is under-specified and contentious among checkers.
- Jelle and Carl noted type checkers differ on whether float covers ints and how coercions should be handled.