[LarsDu88]

`uv` is not a drop-in replacement for `conda` in the sense that `conda` also handles non-python dependencies, has its own distinct api server for packages, and has its own packaging yaml standard.

`pixi` basically covers `conda` while using the same solver as `uv` and is written in Rust like `uv`.

Now is it a good idea to have python's package management tool handle non-python packages? I think that's debateable. I personally am in favor of a world where `uv` is simply the final python package management solution.

Wrote an article on it here: https://dublog.net/blog/so-many-python-package-managers/

[traversaro]

I am not sure pixi uses the same solver of uv, at least in general. pixi uses resolvo (https://github.com/mamba-org/resolvo) for conda packages, while uv (that in turns uses pubgrub https://github.com/pubgrub-rs/pubgrub) for pip packages.

[LarsDu88]

Pixi uses uv for resolving pypi deps: https://prefix.dev/blog/uv_in_pixi If you look closely, pixi used `resolvo to power `rip` then switched from a `rip` solver to a `uv` solver

[LarsDu88]

Hmmm I'll update that point

[immmmmm]

I have been using pixi for half a year and it has been fantastic.

It’s fast, takes yml files as an input (which is super convenient) and super intuitive

Quite surprised it isn’t more popular

[Balinares]

Bookmarking. Thanks for sharing the link, looks like a great overview of that particular tragic landscape. :)

Also crossing fingers that uv ends up being the last one standing when the comprehensive amounts of dust here settle. But until then, I'll look into pixi, on the off chance it minimizes some of my workplace sorrows.