You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ pyenv local miniconda3-latest
$ ./createmodule.sh /opt/intel/parallel_studio_xe_2020/psxevars.sh intel64 | grep CONDA
Unhandled change of CONDA_PREFIX
Before </home/werner/.repo/github.com/pyenv/versions/linux-x86_64/miniconda3-latest>
After </opt/intel/intelpython3>
Unhandled change of CONDA_PYTHON_EXE
Before </home/werner/.pyenv/versions/miniconda3-latest/bin/python>
After </opt/intel/intelpython3/bin/python>
Unhandled change of CONDA_SHLVL
Before <0>
After <1>
Unhandled change of CONDA_EXE
Before </home/werner/.pyenv/versions/miniconda3-latest/bin/conda>
After </opt/intel/intelpython3/bin/conda>
Unhandled change of CONDA_DEFAULT_ENV
Before <root>
After <base>
setenv CONDA_PROMPT_MODIFIER (base)
As you can see, the latter will fail to do the job.
Any hints?
Regards
The text was updated successfully, but these errors were encountered:
Thanks for the report. createmodule.sh finds some variables changed during the execution of the analyzed shell script and does not handle this situation. Outputing a setenv statement with the value set during shell script evaluation should be more appropriate.
Hi,
I use pyenv to manage python versions, and I installed the miniconda-lastest with pyenv.
Then I do the following testing on createmodule.sh within and outof the pyenv-based conda environment:
Outside of the pyenv-based conda environment:
Within the pyenv-based conda environment:
As you can see, the latter will fail to do the job.
Any hints?
Regards
The text was updated successfully, but these errors were encountered: