Re:Are you expected to run five Python type-checkers now?
by ethagnawl on Monday June 08, 2026 @11:29AM
(#48446663)
Yeah, I can't say I really get the appeal of gradual typing. It's commented/documented code at best and outright lies at worst. Sure, you can build tooling around it and improve your DX a bit but isn't it always a house of cards?
[ Parent
| on HN ]
Re:Are you expected to run five Python type-checkers now?
by ocamoss on Monday June 08, 2026 @12:01PM
(#48447098)
> commented/documented code at best
Machine-checked documentation is always valuable, IMO
Re:Are you expected to run five Python type-checkers now?
by falcojr on Monday June 08, 2026 @03:03PM
(#48449936)
If you add one of these type checkers into your CI or a pre-commit hook, it provides the same guarantees you get from a compiler along with the same tooling benefits. It gives you the option of using the structure when you need it, but not being forced to use it when you want to take advantage of some of the more dynamic features of the language.
Re:Are you expected to run five Python type-checkers now?
by chuckadams on Monday June 08, 2026 @03:12PM
(#48450113)
But none of the runtime benefits of having static types in the compiler, since the runtime still can't trust the types. Still, half a loaf is better than none.