Bringing uv and ty together

I love Astral’s tools, but I wonder why the CLI feels so fragmented.

- Now, ty is integrated into uv, while ty is technically being part of ruff [1], but ruff is not integrated into uv.

- The formatter is part of ruff, but uv also have an undocumented "format" command, which does not produce the same results.

- Actually, ruff is part of uv, but you must call it through "uv tool run ruff".

I guess I'd like "uv format" and "uv lint" to become the standard commands.

[1] https://github.com/zed-extensions/pyrefly/issues/26#issuecom...

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.

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.

It seems like it would make more sense for ty to be integrated with ruff than uv.

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 ..

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.

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!

I fundamentally appreciate the single tool toolchain but ty‘s hesitant support of Django(’s quirks) preempts the advantages for me.

I'm really glad that unlike most other recent acquisitions, OpenAI's acquisition of Astral had seemingly no negative impact on their products

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

what happened to pyx?

[flagged]

[dead]

[flagged]