Some questions/suggestions (if these are implemented, please just close/check off): - [ ] Does/can `set_python_env()` overwrite the configuration file to point to the new env, such that the user does not need to first run `reset_rMIDAS_env()`? - [ ] Could we add a default argument like "temporary=FALSE" to determine whether the config is rewritten permanently for future loads? - [ ] Can we add the alias `set_rMIDAS_env()` for `set_python_env` to be consistent with `reset_` and `delete_` functions - [ ] If so, we can then deprecate `set_python_env()` for v1.0
Some questions/suggestions (if these are implemented, please just close/check off):
Does/can
set_python_env()overwrite the configuration file to point to the new env, such that the user does not need to first runreset_rMIDAS_env()?Can we add the alias
set_rMIDAS_env()forset_python_envto be consistent withreset_anddelete_functionsset_python_env()for v1.0