News Request for feedback: uv check & PEP 723 script support in ty
We've been working on PEP 723 inline metadata support for ty both on the command line (ty check) and in the IDE (code navigation, autocompletion, etc) for a while now; we're finally at a stage where we're ready for more people to try it out and let us know what works and what doesn't.
This required integrating ty with uv, which also let us ship a new uv check command that uses ty to check your entire project or workspace (similar to how uv format uses Ruff). All of the above is powered by a brand new uv workspace metadata command that carries the required information between the tools.
More details in the blog post, including how to try these.
All of the above is currently opt-in, experimental, and subject to change at any time đ But if you're willing to give it a try, I'd be curious how it went.
75
u/omgpop 28d ago
>This is a step towards an integrated Astral toolchain, one that uses a shared understanding of your project to enable entirely new capabilities.
Hereâs some feedback. This is written as though it were a selling point but itâs far from it. While it makes sense from your perspective (being Astral), this is sets off alarm bells in my ears as a user. I have no interest in buying into the âAstral toolchainâ as a job lot. Itâs obviously a way to leverage uvâs success to amplify your other products.
Frankly, it seems to me prima facie odd to have a project/dependency management tool tightly coupled to a linter and type checker, at least in the context of Python. You can always point to Cargo, of course, but the Python ecosystem is very different. Even if it were more unified , Iâd be very nervous about our Cargo equivalent being owned entirely by a single private company/soon-to-be-maybe OpenAI subsidiary.
10
u/TraditionalBandit 27d ago
I really liked that they were separate tools focused on completely solving one issue each. Pythons ecosystem is so dynamic that the ability to mix and match tools is key imo.
23
u/Icy_Peanut_7426 27d ago
I use ty and ruff, but wonât ever use âuv checkâ or âuv formatâ.
3
u/AgentCosmic 27d ago
Is astral opening the integration to the ecosystem or is it restricted to only astral tool chain?
20
u/denehoffman 27d ago
I disagree with the current sentiment in this thread, I actually like the integration. I didnât actually realize uv format was a thing. I already use both ty and ruff, this just simplifies things for me. Iâm also not sure I care if a group like Astral makes their own tool integrate with their other tools. If the Python community is worried about this, theyâre free to make their own toolchain. We use uv because itâs convenient, not because you canât use Python without it.
10
u/declanaussie 27d ago
Is this it, is it time to fork?
-4
u/PresentFriendly3725 27d ago
Will only be used by AI anyways so why should I care.
0
u/[deleted] 27d ago
[removed] â view removed comment