[1] https://github.com/astral-sh/ty/commit/7a6b79d37e165f2e73189...
Still, it's great that this is being worked on and I expect in a year or two ty should be comprehensive enough to migrate over to.
my understanding is no real news on Ty since then? is Astral announcing it as production ready?
Then "Release post will cover all of this" in reply to a question asking for a detailed comparison to alternatives: https://x.com/charliermarsh/status/1995163183808643466
I'm saying that as a massive uv and ruff fan.
I want my tools to be interchangeable and to play well with other choices.
Having multiple big players helps with that.
Competition is good in this case.
Previous discussion:
Ty: A fast Python type checker and language server - https://news.ycombinator.com/item?id=43918484 - May 2025 (287 comments)
1. packaging with uv (instead of pip or poetry),
2. type checking with ty (instead of the default MyPy or Meta's Pyrefly),
3. linting with ruff (instead of Jedi),
4. building with uv build (instead of the default setuptools or poetry build),
5. and publishing with uv publish (instead of the default twine)
...and I'm just here to just say that I highly recommend it!
Obviously obsessing over type checking libraries can quickly become bikeshedding for the typical project, but I think the cohesive setup ends up adding a surprising amount of value. That goes double if you're running containers.[1]
TBH I see Astral and Pydantic as a league of their own in terms of advancing Python, for one simple reason: I can trust them to almost always make opiniated decisions that I agree with. The FastApi/SQLModel guy is close, but there's still some headscratchers -- not the case with the former two. Whether it's docs, source code, or the actual interfaces, I feel like I'm in good hands.
TL;DR: This newly-minted fanboy recommends you try out ty w/ uv & ruff!
[1]https://docs.astral.sh/uv/guides/integration/docker/#availab...
code_biologist•51m ago
@dang or another mod, can you add that to the title? Thanks!