Search notes:

Conda

Installing miniconda

I had some success to install miniconda like so:

mkdir -p ~/miniconda3
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O ~/miniconda3/miniconda.sh
bash ~/miniconda3/miniconda.sh -b -u -p ~/miniconda3
rm -rf ~/miniconda3/miniconda.sh

~/miniconda3/bin/conda init bash

List available environments

conda env list
conda info --envs

It seems that environments are stored under ~/miniconda3/envs, but see also ~/.conda/environments.txt

Switching to a given environment

conda activate ‥

Exiting an environment

(base) $ conda deactivate
$

Removing an environment

conda env remove --name pypi-preparation

Create a new environment and install packages in one go

conda create --name pypi-preparation  build twine -y

Then‥

conda activate pypi-preparation

No pip after creating a new environment with a specific python version (?)

Once, it seemed I had no pip anymore after installing a new environment. However, I was unable to reproduce this behavior with the follwoing command:

(base) $ conda create -n renes-modules python=3.14
(base) $ conda activate renes-modules

No more pip (not anymore)

(renes-modules) $ which pip

pip needs to be installed:

(renes-modules) $ conda install pip

List all packages in the current environment

conda list

TODO

/home/rene/miniconda3/bin vs /home/rene/miniconda3/condabin

Environment variables:

`CONDA_EXE`	`/home/rene/miniconda3/bin/conda`
`CONDA_PREFIX`	`/home/rene/miniconda3`
`CONDA_PROMPT_MODIFIER`	`(base)`
`_CE_CONDA`
`CONDA_SHLVL`	`1`
`CONDA_PYTHON_EXE`	`/home/rene/miniconda3/bin/python`
`CONDA_DEFAULT_ENV`	`base`

Why does conda modify ~/.bashrc? Is this necessary and/or can it be turned off?