Between uv and pixi, I’ve had a much easier time than trying to juggle conda, pip, and mamba. I enjoyed your packaging pain article and I’m stoked that the tools built by Rustaceans are just too easy to install from source.
I used mostly uv myself, but I would not recommend a tool that just came out because I don't know the consequences for others.
The Python community is extremely diverse, and some groups hit walls you have no idea even exist, so I usually wait a year or two before I can have a grip on the big picture.
It preserves the global namespace. `uv pip install` is for a pip-like API. You know what you get without even looking at the doc. But one day, they will likely add a `uv install` that is specific to uv, and will behave differently, fixing the flaws of other tools like pip.
Thanks for the thoughtful response. I appreciate it, but not sure I buy it. The grammar for pip is tiny. I code in Python and C#, to completely different grammars, and I'm capable of keeping those differences in my head. And can translate between them if necessary.
I'm quite capable of knowing that "pip install" is the command I use when using pip, and "pdm add" is what I use when using pdm, and could likely even manage to remember that "uv include" might be a keyword I use if using uv.
As an aside your post reminded me that I needed to check out ruff. I discovered that they now provide a VSCode package and I installed it yesterday. So far so good.
Between uv and pixi, I’ve had a much easier time than trying to juggle conda, pip, and mamba. I enjoyed your packaging pain article and I’m stoked that the tools built by Rustaceans are just too easy to install from source.
I used mostly uv myself, but I would not recommend a tool that just came out because I don't know the consequences for others.
The Python community is extremely diverse, and some groups hit walls you have no idea even exist, so I usually wait a year or two before I can have a grip on the big picture.
Why "uv pip install <package name>"
Too many extras words turn me off.
We are not using pip so why the pip keyword?
It preserves the global namespace. `uv pip install` is for a pip-like API. You know what you get without even looking at the doc. But one day, they will likely add a `uv install` that is specific to uv, and will behave differently, fixing the flaws of other tools like pip.
Thanks for the thoughtful response. I appreciate it, but not sure I buy it. The grammar for pip is tiny. I code in Python and C#, to completely different grammars, and I'm capable of keeping those differences in my head. And can translate between them if necessary.
I'm quite capable of knowing that "pip install" is the command I use when using pip, and "pdm add" is what I use when using pdm, and could likely even manage to remember that "uv include" might be a keyword I use if using uv.
As an aside your post reminded me that I needed to check out ruff. I discovered that they now provide a VSCode package and I installed it yesterday. So far so good.
Now if only they could make my Django test suite faster.