ty Python type checker

“It's a good default for a pre-1.0 tool that aims to type check existing code.”

“A large fraction of the findings were ty guessing the type and being wrong.”

“It's cool to see ty support for scripts. That's something I really needed”

“even now aren't adding support until after `ty` is integrated”

“ty‘s hesitant support of Django(’s quirks) preempts the advantages for me.”

“One step closer to bringing the Rust experience to Python. Good.”

“having them as a first class feature of the package manager will save so much unnecessary pain”

“With the possible exception of ty since that's still pretty new”

“Great to see ruff, ty and uv being actively developed”

“ty seems to work better, and is not a one man show/bus factor of 1”

“Went from type checking taking ~10 minutes in CI to now taking ~15 seconds and runs on pre-commit.”

“other than `uv` and `ty`, I don't feel a whole lot has improved in Python land”

“rust-based tools (ty, pyrefly) have popped up, running sub-second.”

“There are plenty of options for static type checking in Python. Choose your favorite or just use Ty”

“Ty is quantitatively the worst of the well-known type checkers”

“wondering if I can ever work another python project after having experienced uv, ruff, and ty”

“Ty, Ruff, UV, all great tools I recently started really using”

“it's nice to know that uv (+ ty and many others) and Bun will stay maintained”

“ty sometimes finds real issues that are actually allowed by the spec”

“Given the quality of uv and ruff and the experience of the team working on ty, I'm quite confident it's going to be great in that respect as well.”

“you'll get clear diagnostics for that particular example”

“I am worried about the false negatives/positive rate however.”

“And it makes it infinitely easier for them to get with thr times and start typing their code!”

“It does a good job of being fast and easy to use while catching many issues without being overly draconian.”

“If you're starting a new project, there's no reason you shouldn't.”

“the type safety/security issues can hopefully be mitigated by ty and pyodide”

“I immediately set up up ruff, ty, pytest, pre-commit hook and GH workflow to run ruff/ty/pytest”

“It is definitely not as good, but it is also really new.”

“Python can type check single file scripts (even with PEP 723 deps) with ty”

“It's not great, but in this very thread there's a person from the conformance team”

“"rust inspired" diagnostics that are extremely helpful”

“Django support will be a game changer on top of the game changer ty is!”

“it doesn't work well with TypedDicts and that's a show-stopper for us”

“I'd be tempted to use this solely due to their support of intersection (A & B) types”

“ty immediately found issues where we annotated that a duct was an acceptable input, but actually doing so would break things.”

“Ty doesn't support Django yet, and it doesn't have a plugin system, so third party developers can't improve it.”

“Very exciting! I guess I'll have to wait for Django and Pydantic support to migrate to it”

“ty is actually a big step in this direction as it provides multi-file analysis and type inference.”

“TIL that ty is also a language server, which means it replaces not only mypy, but also Pyright”

“It's still very far from being competitive with SOTA type checkers like basedpyright.”