Re:Escaping from Anaconda's Stranglehold on macOS
by teruakohatu on Sunday September 01, 2024 @10:44PM
(#41422215)
> Then, adopt `uv` instead, for all your Pythons: https://docs.astral.sh/uv/
uv looks great, but its coming from a VC-backed company with no apparent way to monetise. Discussion here:
Re:Escaping from Anaconda's Stranglehold on macOS
by mirashii on Sunday September 01, 2024 @10:48PM
(#41422230)
It's licensed MIT and Apache 2.0. The community can fork it if it ever becomes an issue.
Re:Escaping from Anaconda's Stranglehold on macOS
by eddyg on Monday September 02, 2024 @03:05PM
(#41427972)
Yet.
You have no idea what Astral’s other (future) plans include. For example, what if they are working on all this tooling so they can start providing “verified, reproducible Python packages” as a service, to mitigate against supply chain attacks?
Telling people not to use Astral’s products because they are VC-backed is silly, especially since everything they’ve done so far is permissively licensed.
Arguably step one is: https://docs.anaconda.com/anaconda/install/uninstall/
Or for miniconda: https://gist.github.com/pulkitgangwar/421a1af800c5a9c6d4a77b...
Then, adopt `uv` instead, for all your Pythons: https://docs.astral.sh/uv/
The 2024-08-24 update finally does "all the things" — unified Python packaging: https://astral.sh/blog/uv-unified-python-packaging
. . .
PS. I noticed this original article's subsequent blog post gets into "env as code" but for "one tool to rule them all" one may want to consider a tool such as `mise` instead: https://mise.jdx.dev/about.html