use conda env config vars set about conda-devenv HOT 2 OPEN

I was not aware of that sub command. Its is good to be make aware of that.

But I see 2 problems:

1. Today conda-devenv will append when an environment variable is declared as list and not overwrite. This is usefull when one want to do things like add a path to PATH or PYTHONPATH;
2. (More of a personal opinion) Today one could use conda-wrappers that will create wrapper scripts (eg. \Scripts\wrappers\conda\python.bat) to perform a quick activation and execute the environment's python, and that do not process the "state" file but execute the activation scripts;

from conda-devenv.

I was not aware of that sub command. Its is good to be make aware of that.

But I see 2 problems:

1. Today conda-devenv will append when an environment variable is declared as list and not overwrite. This is usefull when one want to do things like add a path to PATH or PYTHONPATH;
2. (More of a personal opinion) Today one could use conda-wrappers that will create wrapper scripts (eg. \Scripts\wrappers\conda\python.bat) to perform a quick activation and execute the environment's python, and that do not process the "state" file but execute the activation scripts;

i use conda-wrappers as part of my 'system' (it's great!). i just feel that this env var concept should be integrated. ya, the wrapper scripts don't activate the conda env config vars vars. so i dropped the idea for my use.

from conda-devenv.