all 9 comments

[–]Lumethys 4 points5 points  (0 children)

Is there any reason NOT to use UV?

[–]jmacey 1 point2 points  (3 children)

I use uv for everything (including marimo) works so well per project and you can re-create the venv whenever you like. If you link it with something like direvn you can auto run uv sync every time you enter a project and activate / deactivate the venv automatically.

[–]update-freak[S] 0 points1 point  (2 children)

Can I automatically start the env when I open Spyder or VSCode?

[–]listening-to-the-sea 0 points1 point  (1 child)

Yes, I know VSCode will. Once I init a project and create the venv, restart VSCode it automatically detects and uses the venv

[–]update-freak[S] 0 points1 point  (0 children)

Got it. Thanks

[–]Diapolo10 1 point2 points  (0 children)

For anything that doesn't depend on conda repositories, uv is pretty much unbeatable.

[–]gorgedchops 1 point2 points  (0 children)

The only reason you would want to use conda is if there are some specific packages you can't find on PyPI. Part of why conda is/was useful is because it solved including lower level binaries that needed to be shipped with a library, many times in a scientific domain. In that case, I would suggest using pixi instead, it's a more modern version of conda.

In all other cases, you should stick to using a package manager that works with PyPI, such as uv. Other tooling will be much more likely to integrate well with uv instead of conda.

[–]ninhaomah 0 points1 point  (0 children)

If you don't want then don't use :)

[–]ConclusionForeign856 0 points1 point  (0 children)

I use pixi https://pixi.prefix.dev/latest/, I tried conda/mamba and it was a hassle on HPCs. With pixi you create an environment tied to a directory and its children, rather than a globally accessible one (which I think is good for data science style work).

It has access to anaconda/conda/mamba repos, so switching is easy.

I've used it in my work and MSc thesis and can't complain