What does the Astral team recommend for setting up their tools on a new machine? Install uv with curl, manage python versions and projects from there and install ruff with uv?
Uv 0.3 – Unified Python packaging
21–30 of 60 posts
Re: Uv 0.3 – Unified Python packaging
#22https://xkcd.com/927/
That was my instinctive reaction as well, but as others have pointed out, the team does have credibility from e.g. the Ruff linter.
Re: Uv 0.3 – Unified Python packaging
#23What does the Astral team recommend for setting up their tools on a new machine? Install uv with curl, manage python versions and projects from there and install ruff with uv?
Yeah, I think so. Their documentation includes a note on how to bootstrap from a fresh Docker image here: https://docs.astral.sh/uv/guides/integration/docker/
Re: Uv 0.3 – Unified Python packaging
#24What does the Astral team recommend for setting up their tools on a new machine? Install uv with curl, manage python versions and projects from there and install ruff with uv?
Not on the Astral team, but to the first step, I'd get uv from your distro package manager (e.g. https://build.opensuse.org/package/show/openSUSE:Factory/uv) and then the rest as you say ("manage python versions and projects from there and install ruff with uv").
If you have some other tool manager on your system (e.g. mise) then you can likely install uv through that.
Re: Uv 0.3 – Unified Python packaging
#25What's the recommended/opinionated
This:
Re: Uv 0.3 – Unified Python packaging
#26https://xkcd.com/927/
I think they meant "unified" here in the same sense in which BusyBox is unified, i.e. several things you'd normally use different tools for combined into one executable/project. They're not trying to invent any new standards, most of these tasks already have PEPs that the existing tools and uv both implement. Maybe not the best word choice though because I normally have the same instinctive reaction in response to someone claiming something is "unified".
Re: Uv 0.3 – Unified Python packaging
#27I've been closely following the Astral team's work. I am excited by this release and look forward to trying out uv again.
I have been working with python for over 10 years and have standardized my workflow to only use pip & setuptools for all dependency management and packaging [1]. It works great as a vanilla setup and is 100% standards based. I think uv and similar tools mostly shine when you have massive codebases.
Re: Uv 0.3 – Unified Python packaging
#28https://xkcd.com/927/
Unfortunate that python dev these days requires dependency manager managers to set up an entire for-purpose python just for each project. As opposed to being able to run on the system python (like every other scripting language). A victim of it's popularity.
Now since Uv is in Rust we'll need a dependency manager manager manager for it on any OS that's not rolling to compile since what rustc is changes every 3 months and breaks forwards compatibility.
I'll check back in in 3 years (3x longer than Astral has so far existed) and see if Uv still exists and has become stable enough to use.
Re: Uv 0.3 – Unified Python packaging
#29Does it support building native extensions and Cython modules or are setuptools still the only reasonable way to do this?
Does it support Numpy and Pytorch?
Re: Uv 0.3 – Unified Python packaging
#30Earlier quoted context omitted.
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.
Aren't they the same team?
Rye was a one man project by mitsuhiko before it was adopted by astral. I think it's basically just his work.