Nash JC - NCF via linux wrote on 2026-05-14 12:38:
I think I've a solution, but welcome comments about potential problems.
I followed miniconda3 installation instructions. On restarting
terminal after
installation, the venv for conda was active, i.e., the "(base) "
prefix to the
terminal prompt was there.
I then added to .bashrc the 4 lines between the dashes
-------------------------------------------
# start with conda NOT running
conda deactivate
echo "To activate conda issue 'conda activate'"
-------------------------------------------
Now I can activate conda with the indicated command or
do 'conda deactivate' to get back to normal.
Is this sensible?
I haven't used conda but yes, looks good.
Can't imagine why auto-invoking a venv in .bashrc was thought a good
idea. That would co-mingle a bunch of virtual environments together,
kind of defeating their purpose (other than keeping the host OS's Python
untouched).