I think the push has been entirely organic. Compared to existing tooling, uv is fantastically fast.

One of the bigger pain points I’ve faced in Python is dependency resolution. conda could take 30-60 minutes in some cases. uv took seconds.

A serious quality of life improvement.

▲

edelbitter 5 hours ago | parent | next [-]

> dependency resolution. conda could take 30-60 minutes

Quite literally this is what first raised the alarm bells for me. Dependency resolution complexity is more of a symptom. If that delay ends up being the point where Ops finally agrees that things have gone very wrong, then fixing that delay is not really helping hire the maintenance folks that can make those dependencies.. well, "dependable" again.

▲

optionalsquid 6 hours ago | parent | prev [-]

uv replaces pip (and venv, and pipx, and more), not conda. If you want a uv-equivalent that replaces conda, then look at pixi: https://pixi.prefix.dev/

▲

moregrist 6 hours ago | parent [-]

Sure, it replaces pip, but _we used conda_ for env management. And the slow part was still _dependency resolution_, much like pip.

Was there a better option? I’m sure. Choices were made. Regrets were had. Switching to uv was a huge improvement for our purposes.

	▲	optionalsquid 2 hours ago \| parent [-]
		If all you are installing using conda is pypi packages and different versions of Python, then sure, uv is a fine replacement. I use it for that as well. But if you are using other conda/conda-forge/bioconda packages, then uv isn't a replacement since it cannot install those. However, Pixi can replace conda for that use-case and it's about as fast as uv since it uses uv's dependency resolution code