Unsetting of environmental variables is not fully working. #10171
Comments
angloyna
added
source::community
|
Further info: The environmental variable was an email, maybe the |
|
dont think so, i have the same problem with the GOOGLE_APPLICATION_CREDENTIALS var, where the value is just the path to the file |
|
Having a similar issue where the environment variable has a "==" in it. |
|
I messed up the setting of my environment variables when using Fixed issue by directly editing the value in |
|
It appears that environment variables that are created for an environment using Both of these behaviors in conjunction create a situation where an invalid environment variable can be supplied once, unset, and then complain about the identifier being invalid every time the environment is activated. Steps to reproduce
Example: $ conda create -y -n conda-test
Collecting package metadata (current_repodata.json): done
Solving environment: done
==> WARNING: A newer version of conda exists. <==
current version: 4.10.3
latest version: 4.11.0
Please update conda by running
$ conda update -n base -c defaults conda
## Package Plan ##
environment location: /home/madison/programs/anaconda3/envs/conda-test
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
#
# To activate this environment, use
#
# $ conda activate conda-test
#
# To deactivate an active environment, use
#
# $ conda deactivate
$ vact conda-test
$ conda env config vars set not::valid::identifier
To make your changes take effect please reactivate your environment
$ deac
bash: unset: `not::valid::identifier': not a valid identifier
$ vact conda-test
bash: export: `NOT::VALID::IDENTIFIER=not::valid::identifier': not a valid identifier
$ conda env config vars unset not::valid::identifier
To make your changes take effect please reactivate your environment
$ conda env config vars list
$ deac
bash: unset: `not::valid::identifier': not a valid identifier(here Similar to @IrfanAkram5, the only way I was able to get these complaints to go away was manually editing the |
|
Hi there, thank you for your contribution! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment. Thanks! |
|
This issue still persists using the instructions I described above. |
|
Not stale |
github-actions
bot
added
stale::recovered
kenodegard
added
type::bug
|
If you need to remove a previously configured environment variable please modify the state file. |
|
What's the proper way to modify the state file? |
Current Behavior
Hi, I set an environment variable via
conda env config vars set my_var=valueand then unset it viaconda env config vars unset my_var -n test-env.The variable is now not listed anymore under
conda env config vars listbut when I runconda update --allone of the outputs is(eval):unset:2: old-variable-name: invalid parameter name.Steps to Reproduce
Included above.
Expected Behavior
Running
conda env config vars unset my_var -n test-envshould fully delete the variable.Note: I also receive the following error, but I cannot fix that, no matter what I have tried, maybe it's connected:
Environment Information
`conda info``conda config --show-sources``conda list --show-channel-urls`The text was updated successfully, but these errors were encountered: