2 ms·
Why not? Have mypy/pyright/pryefly/ty type errors break CI. If you're starting a new project, there's no reason you shouldn't.
by maleldil 7mo ago
Why not? Have mypy/pyright/pryefly/ty type errors break CI. If you're starting a new project, there's no reason you shouldn't.
- ashishb 7mo ago> Have mypy/pyright/pryefly/ty type errors break CI. Only if types are present. > If you're starting a new project, there's no reason you shouldn't. Most dependencies would still be untyped.
- maleldil 7mo ago> Only if types are present. Make sure they are. Set no implicit any in your type checker, and use a linter to ensure every function has type annotations. > Most dependencies would still be untyped Most is a big exaggeration. I understand it's dependent on the domain, but only a small subset of the ones I use in my projects are untyped, and you can write typed wrappers when necessary. Also, perfect is the enemy of the good. I'd rather have a 90% typed codebase and work around untyped dependencies than abandon the idea at all.