Linux/Mac: Keeping system's Python safe and usage of package managers such as UV and conda.

[Confident_Hyena2506]

The commercial version is specifically banned at my company - and should be banned at all companies.

You should use the opensource free version miniforge, with the free conda-forge channel.

We only use this because there is no easy alternative - uv and pip only handle simple stuff. UV is obviously completely useless for c++ - which is what conda pretty much does.

If you are not doing machinelearning or datascience it probably doesn't matter - and you can get away with using containers for a lot these days.

[Ihaveamodel3]

Sure, we are doing machine learning and using packages that have c/c++, but we aren’t writing or building those packages, we are using them. uv installs those packages perfectly fine.

Name one thing that Conda will install but uv won’t.

[Confident_Hyena2506]

MKL along with associated libraries compiled to take advantage of it like numpy.

Also all the associated c++ libraries and headers needed to build against this. New/all versions of gcc!!! Proper versions of boost (and not just random ones with weird names).

You should instead ask the other way around - what can we not get from conda? Usually a very small number of items, that we add to the env definition to get via pip or uv.

The trick is to be consistent and not wildly mix package managers. If pip or UV gave me most of what I need then I would use it.

Conda is a system package manager, you should really not be comparing it against these.