Live data from Hacker News

Uv's killer feature is making ad-hoc environments easy

valatka.dev

51–60 of 428 posts

Re: Uv's killer feature is making ad-hoc environments easy

#51

uv has does not (nor do they plan to add) support for conda, and that is a deal-breaker.

I can't see why anyone is using Conda in 2025. In 2018, yeah, pip (now uv) was hard and you could get a "just works" experience installing Tensorflow + NVIDIA on Conda. In 2023 it was the other way around and it still is.

Re: Uv's killer feature is making ad-hoc environments easy

#53
post #26

As a NodeJS developer it's still kind of shocking to me that Python still hasn't resolved this mess. Node isn't perfect, and dealing with different versions of Node is annoying, but at least there's none of this "worry about modifying global environment" stuff.

It is kind of solved, but not default.

This makes a big difference. There is also the social problem of Python community with too loud opinions for making a good robust default solution.

But same has now happened for Node with npm, yarn and pnpm.

Re: Uv's killer feature is making ad-hoc environments easy

#54

uv has does not (nor do they plan to add) support for conda, and that is a deal-breaker.

Why would it be a deal breaker? uv would replace conda. And I hope it does. Conda has been such a headache for me when I've used it in the past. If the Python (particularly ML/academic community) could move on from conda it would be a great thing.

Re: Uv's killer feature is making ad-hoc environments easy

#55
I honestly really hate the venv ergonomics but uv does still depend on it as the golden path if you don’t use the —with flags (in my understanding). Is there a way to do a clean break with just the new —script inline dependencies, or is that wrong/suboptimal?

Re: Uv's killer feature is making ad-hoc environments easy

#56

uv has does not (nor do they plan to add) support for conda, and that is a deal-breaker.

I can't see why anyone is using Conda in 2025. In 2018, yeah, pip (now uv) was hard and you could get a "just works" experience installing Tensorflow + NVIDIA on Conda. In 2023 it was the other way around and it still is.

Well, when you're building python packages that have non python dependencies and a big chunk of your users are on Windows, conda is the only option, even in 2025 :)

Examples include, quant libraries, in-house APIs/tools, etc.

Re: Uv's killer feature is making ad-hoc environments easy

#57
post #26

As a NodeJS developer it's still kind of shocking to me that Python still hasn't resolved this mess. Node isn't perfect, and dealing with different versions of Node is annoying, but at least there's none of this "worry about modifying global environment" stuff.

Because node.js isn't a dependency of the Operating system.

Also we don't have a left pad scale dependency ecosystem that makes version conflicts such a pressing issue.

Re: Uv's killer feature is making ad-hoc environments easy

#59
post #50

wow, they've re-invented a tiny bit of Nix, purely legend!

That you can use without having 4 PhDs. It's pretty good. You should try it sometime when your done fully ingesting algebraic topology theory or whatever the fuck Nix requires to know just to install figlet.

Oh come on, it's not that hard even for packaging stuff (let alone usage). Quite trivial compared to leetcode grind I'd say.

Re: Uv's killer feature is making ad-hoc environments easy

#60
post #22

Earlier quoted context omitted.

I never used anything other than pip. I never felt the need to use anything other than pip (with virtualenv). Am I missing anything?

Pip doesn't resolve dependencies for you. On small projects that can be ok, but if you're working on something medium to large, or you're working on it with other people you can quickly get yourself into a sticky situation where your environment isn't easily reproducible. Using uv means your project will have well defined dependencies.

https://pip.pypa.io/en/stable/topics/dependency-resolution/
Post reply on HN