Executive Summary
Mypy, Pyrefly, Pyright, ty, Zuban, and possibly more that will come in the future... how are library maintainers expected to cope? TL;DR: Prioritise running as many type-checkers as possible on your test suite. Run at least one on your source code. The type checking that matters most (and why you've probably got it backwards) If you only read one section of this blog post, please make it this one. Because this is where a lot of packages get it wrong. It's common to see packages run type checkers on their source code and to leave their tests untyped. That approach has it backwards. Suppose you
Source Coverage
| Source | Headline | Published At |
|---|---|---|
| Hacker News – Front Page | Are you really expected to run five type-checkers now? | Pyrefly |
| FreightWaves | Black Marker, Magnetic Signs, and Peeling Decals: Here Is What 49 CFR 390.21 Actually Requires. | 2026-06-05 00:00:00+00:00 |
Timeline
- 2026-06-03 00:00:00+00:00: Are you really expected to run five type-checkers now? | Pyrefly (via Hacker News – Front Page)
- 2026-06-05 00:00:00+00:00: Black Marker, Magnetic Signs, and Peeling Decals: Here Is What 49 CFR 390.21 Actually Requires. (via FreightWaves)