You might want to reconsider your use of Anaconda / Conda. Updated terms of service are unclear about what is and isn't allowed under their free tier, with potential of contamination of "off limits" packages due to dependency resolution (using environment files).
https://www.theregister.com/2024/08/08/anaconda_puts_the_squeeze_on
Anaconda puts the squeeze on data scientists now deemed to be terms-of-service violators
Academic, non-profit organizations told to start paying up – or elseThomas Claburn (The Register)
This entry was edited (2 months ago)
PizzaTorque
in reply to Koen Hufkens, PhD • • •Koen Hufkens, PhD
in reply to PizzaTorque • • •PizzaTorque
in reply to Koen Hufkens, PhD • • •Koen Hufkens, PhD
in reply to PizzaTorque • • •Frank Aylward
in reply to Koen Hufkens, PhD • • •Marcos Huerta
in reply to Koen Hufkens, PhD • • •Koen Hufkens, PhD
in reply to Marcos Huerta • • •@marcoshuerta Ow, thanks for this! I didn't look for alternatives yet and this might just deal with all the concerns I have.
I mentioned on LinkedIn that the backlash might be swift with people pivoting to alternatives fast, but I didn't know the ecosystem was already in place.
Marcos Huerta
in reply to Koen Hufkens, PhD • • •The `conda` package manager (and mamba) are BSD-3, so Anaconda's TOS only apply to their repository/channels. miniforge uses the conda package manager, but the default channel is conda-forge (which I prefer anyway...)
conda-forge had Apple Silicon binaries of pandas etc early on, so I've been using their channel via miniforge since I got an M1 Mac Mini a few years back.