The new CREDIT guidance (lines below) to install packages in user space within a conda environment is likely to cause issue for folks (since it's no longer an isolated install w/ the packages in user space). See here: https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#using-pip-in-an-environment
|
```bash |
|
# Casper |
|
conda activate /glade/campaign/cisl/aiml/credit/conda_envs/credit-casper |
|
|
|
# Derecho |
|
conda activate /glade/campaign/cisl/aiml/credit/conda_envs/credit-derecho |
|
``` |
|
|
|
Then clone the repo and install the current branch in editable mode: |
|
|
|
```bash |
|
git clone https://github.com/NCAR/miles-credit.git |
|
cd miles-credit |
|
pip install --user -e . # dependencies already satisfied in the shared env |
|
``` |
|
::: |
I suspect the motivation for this was to be able to provide folks an environment to build off of and then modify at the user level, but I think we might want to approach that differently.
Some options might be:
- having folks clone the starting environment and then edit that
- recommending everyone build their own environments from scratch
If the concern is about the time and space it takes to build new environments, we might look into something like uv or pixi.
The new CREDIT guidance (lines below) to install packages in user space within a conda environment is likely to cause issue for folks (since it's no longer an isolated install w/ the packages in user space). See here: https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html#using-pip-in-an-environment
miles-credit/docs/source/getting-started.md
Lines 13 to 28 in 595cf70
I suspect the motivation for this was to be able to provide folks an environment to build off of and then modify at the user level, but I think we might want to approach that differently.
Some options might be:
If the concern is about the time and space it takes to build new environments, we might look into something like uv or pixi.