| Note |
|---|
This page has been superseded by the following |
...
This page highlights the interplay between using Python and Miniconda on the Beartooth cluster, and how pip/conda install work alongside each other.
...
As a best practice, we would suggest forcing the pip install to locate the package installations into your conda environment folder location and not you home folder.
Setting PYTHONUSERBASE
Previously, the simplest way to do this is to set the following environment variable:
...
| Code Block |
|---|
export PYTHONUSERBASE=$CONDA_PREFIX |
Issue: conda create without defining python
This appears to not work if the created conda environment does not explicitly define it’s own version of python i.e. it’s using the version that comes with miniconda3.
Performing a pip install places the python packages under /apps/u/opt/linux/miniconda3/x.y.z/lib/python3.xx/site-packages/
| Code Block |
|---|
[]$ conda create -p 1.0.0
vs
[]$ conda create -p 1.0.0 python |
Overall Suggestion:
If you’re performing local development, and not sharing, use a module load python/x.y.z - track the version of python and pip install into your local home.
...