Uv 0.3 – Unified Python packaging
astral.sh
Uv 0.3 – Unified Python packaging
1–10 of 60 posts
Re: Uv 0.3 – Unified Python packaging
#2[deleted]
Re: Uv 0.3 – Unified Python packaging
#3Is there any reason to still use Rye, now? looks like this release adds all the things I would have missed from Rye, but I don't think I use all of Rye's features
Re: Uv 0.3 – Unified Python packaging
#4Is there any reason to still use Rye, now? looks like this release adds all the things I would have missed from Rye, but I don't think I use all of Rye's features
I wrote about it a bit here: https://github.com/astral-sh/rye/discussions/1342
Re: Uv 0.3 – Unified Python packaging
#5Is there any reason to still use Rye, now? looks like this release adds all the things I would have missed from Rye, but I don't think I use all of Rye's features
I think uv hits everything that rye does, and with a solid implementation.
With love, rye is all vision, philosophy and duct tape. uv is built by a full-time team.
Re: Uv 0.3 – Unified Python packaging
#6Is there any reason to still use Rye, now? looks like this release adds all the things I would have missed from Rye, but I don't think I use all of Rye's features
There's no equivalent of https://rye.astral.sh/guide/pyproject/#toolryescripts yet, but it's apparently planned: https://github.com/astral-sh/uv/issues/5903#issuecomment-227...
Re: Uv 0.3 – Unified Python packaging
#7It's too bad that the blog post explicitly mentions rye but does not explain how the new features included in uv 0.3 will affect the role that rye will play going forward.
Re: Uv 0.3 – Unified Python packaging
#8Wonder if there’s any reason to stick with hatch or move fully to uv now? Seems maybe hatch still handles the testing matrix whereas uv doesn’t?
EDIT: I still like how hatch allows for defining multiple envs for a given project with the ability to switch between / run in them by name.
Re: Uv 0.3 – Unified Python packaging
#9Congrats! What’s impressive is not just the speed of the tools Astral develops but also the speed of delivery.
I wonder, if you plan to extend the functionality of building and publishing packages. For example, support for dynamic version (from github) and trusted publishers.
Re: Uv 0.3 – Unified Python packaging
#10To me the Astral folks have a lot of credibility because both their ruff linter and formatter have been fantastic. Elevates this kind of announcement from yet another Python packaging thingy to something worth paying attention to.
I like the idea of that single-file Python script with inline dependency info construct, but it's probably going to be a bummer in terms of editor experience. I doubt the typical LSP servers will be aware of dependencies specified in that way and so won't offer autocompletion etc for those libraries.