Bringing uv and ty together (astral.sh)
121 points by Ravencentric 3 days ago
olive-n an hour ago
I feel like pyrefly was gaining some traction over the year. I started using it this week.
This seems like astral realizing they lost the type checker race and now fold it into their popular project so people have a reason to use it.
If it is already installed with uv, people have less reason to look for a type checker and will just stay with the default option.
chippiewill 25 minutes ago
I agree, it sounds like they're trying to expand their moat because they realised they were too late to the better type-checking party.
It's somewhat ironic that they're only just getting around to it actually. The predecessor to `uv`, `rye`, had integration for `ruff` fairly early on - but Astral have really dragged their heels on putting it into `uv` (presumably because `ruff` had already won) and even now aren't adding support until after `ty` is integrated.
WhyNotHugo 7 hours ago
I dislike the idea of these separate tools being blended like this. ty is currently perfectly usable on non-uv projects. uv has *a lot* of opinionated quirks, its custom lockfile lockfile, and other nuances which many of us dislike — ty being a separate tool works fine with plain pip plus any other dependency manager (e.g.: pip-tools).
Of note though, ty doesn't NEED to be integrated into uv, nor vice-versa; keeping them as standalone tools seems most natural.
duskdozer 16 minutes ago
This shouldn't be surprising. Astral has wanted to create lock-in with uv for years and obviously they'll want to bring everyone into their "ecosystem" as much as possible. Stand by for more divergences from main python or use of their "market" capture for leverage over it.
satvikpendem 7 hours ago
A implies B does not mean B implies A too. You can use ty separately, this isn't stopping that, but it is useful for uv check to use ty together.
vovavili 6 hours ago
Projects that use ty for its type checking but something else than uv for managing dependencies are probably in a very tiny minority of users.
jgalt212 6 hours ago
but there's probably lots of projects that use uv, but not ty.
vovavili 3 hours ago
hmartin 4 hours ago
Thank god it has opinionated quirks that old timers dislike.
Otherwise we'd still be stuck in the complete dumpster fire that was the python packaging/venv we had for the previous 20 years.
otherme123 2 hours ago
Old timer here: uv is not the first opinionated tool to manage Python packaging. It is build learning from other tools right and wrongs. I now use uv for everything because its quirks are less disruptive than quirks from previous tools that I also tried and disliked for being a bit too much for a very small gain.
What you call "dumpster fire", I call "steps towards uv", maybe even better tools in the future.
rcleveng 4 hours ago
True, before UV the only way to package python was a container.
disgruntledphd2 2 hours ago
thayne 4 hours ago
It seems like it would make more sense for ty to be integrated with ruff than uv.
NegativeLatency 3 hours ago
I imagine uv will subsume both
bitpush 7 hours ago
I really really love uv but this uv-ty post seems "shipping the org chart"?
They could have just said uv now has type chancing capabilities (or whatever it is ..) ty afaik isn't a super popular brand so the post makes people first understand what ty is ..
dirtbag__dad 6 hours ago
This is what’s up! Having worked on several medium sized python projects where linting and type checking were introduced late in the game, having them as a first class feature of the package manager will save so much unnecessary pain.
IMO, part of the problem is that people just don’t know that linters or tools like this exist at all. This is the best type of product marketing where the product gets meaningfully better, while educating the users for free.
nehalem 2 hours ago
I fundamentally appreciate the single tool toolchain but ty‘s hesitant support of Django(’s quirks) preempts the advantages for me.
xavdid 5 hours ago
Ah, this is great! It's a step towards solving my biggest complaint with PEP 723 scripts: bad editor support.
I loved the idea on paper, but without manually creating a matching venv & installing my deps, I wouldn't get in-editor completions during development. That was fine for small things, but intolerable as the script grew. So it's still not a feature I've used much, since it made more sense to just make a real dev environment.
I'm glad to see there'll be improvements here!
flexagoon 7 hours ago
I'm really glad that unlike most other recent acquisitions, OpenAI's acquisition of Astral had seemingly no negative impact on their products
doot 7 hours ago
It’s barely been 6 months. Give it time.
Kwpolska 19 minutes ago
Don't worry, they'll find a way to enshittify the product at one point. uv went from being a VC-funded tool written in another language (i.e., with a limited contributor pool) to being an AI bubble-funded tool, so it's not something I'd trust would be maintained for a long time.
yoyohello13 3 hours ago
…yet. I’m definitely concerned for the future. Especially because uv is so good. The rug pull is going to hurt a lot.
Philpax 5 hours ago
One step closer to bringing the Rust experience to Python. Good.
LoganDark 4 hours ago
This isn't the Rust experience. Rust still distributes clippy as completely separate from cargo, and rustfmt as separate too, etc. it's technically only rustup that centralizes the distribution of the tools together.
dsp_person 6 hours ago
what happened to pyx?