Post

Jacob Tomlinson
@jacobtomlinson.dev

For Python package management I use a mixture of pixi, uv and conda depending on the task I'm doing. I wrote up a long form post about the history of these tools, why each one exists, and why I settled on these choices in my workflow. jacobtomlinson.dev/posts/2025/p...

jacobtomlinson.devPython package managers: uv vs pixi?When I talk to people about Python package management in 2025 I see the following tools in active use; uv, pixi, pip, conda, mamba, micromamba and poetry. There may be others, but I don’t hear much ab...

21 reposts40 likes

dhirschfeld.bsky.social
@dhirschfeld.bsky.social

I use `pixi` to manage PyPI projects. You don't need to duplicate your dependencies if you're ok with using wheels. `pixi` will automatically map your existing `[project.dependencies]` array to `[tool.pixi.pypi-dependencies]` and will also map `[optional-dependencies]` to `pixi` features.

dhirschfeld.bsky.social
@dhirschfeld.bsky.social

All you need to do is include a `[tool.pixi.workspace]` table in your `pyproject.toml` and you can use `pixi`. The only time I fall back to using `uv` is for thirdparty libraries that don't have a `[tool.pixi.workspace]` defined. To use `pixi` you do need to add (a tiny amount of) extra config.