Jacob Kaplan-Moss kicked off this fascinating conversation about [uv](https://docs.astral.sh/uv/) on Mastodon recently. It's worth reading the whole thing, which includes input from a whole range of influential Python community members …
Why is there often no discussion or mention of Pixi along with uv in conversations about Python tooling? Is it because uv has a lot of VC money to get attention while Pixi doesn’t?
I think short answer is yes, but longer answer is also that Pixi is a drop in replacement for Conda, which is a lot less used than Pip (which uv is a replacement for).
Pixi is more than a drop in replacement for Conda. Pixi being able to replace Conda and do everything that uv does (Pixi has incorporated uv into it’s tools) seems to make it a more complete toolset than uv alone.
Why is there often no discussion or mention of Pixi along with uv in conversations about Python tooling? Is it because uv has a lot of VC money to get attention while Pixi doesn’t?
I think short answer is yes, but longer answer is also that Pixi is a drop in replacement for Conda, which is a lot less used than Pip (which uv is a replacement for).
Pixi is more than a drop in replacement for Conda. Pixi being able to replace Conda and do everything that uv does (Pixi has incorporated uv into it’s tools) seems to make it a more complete toolset than uv alone.