Unable to use a new environment after creating it (PluginError)
#12195
Labels
locked
[bot] locked due to inactivity
pending::support
indicates user is waiting on support from triage engineers
source::community
catch-all for issues filed by community members
type::support
neither a bug nor feature, is really just a user having questions or difficulty somewhere
Comments
javierttgg
added
the
type::bug
|
@javierttgg Hm, yes, this looks related to #12161, can you provide your path before running |
kenodegard
added
type::support
|
@kenodegard thanks for the prompt response. Sorry to ask, with path, are you refering to the path shown in the anaconda prompt? In that case, the path remains the same ( (base) C:\Users\Usuario>conda activate foo
(foo) C:\Users\Usuario>On the other hand the path where the env is created seems usual to me: (base) C:\Users\Usuario>conda env list
# conda environments:
#
base * C:\Users\Usuario\miniconda3
foo C:\Users\Usuario\miniconda3\envs\foo |
conda-bot
added
pending::support
|
@javierttgg my bad, I wasn't clear, I meant your search path. For Anaconda Prompt (which uses echo %PATH%For Anaconda Powershell Prompt (which as the name suggests uses echo $env:Path |
kenodegard
added
pending::feedback
|
@kenodegard ok thanks :) before: (base) C:\Users\Usuario>echo %PATH%
C:\Users\Usuario\miniconda3;C:\Users\Usuario\miniconda3\Library\mingw-w64\bin;C:\Users\Usuario\miniconda3\Library\usr\bin;C:\Users\Usuario\miniconda3\Library\bin;C:\Users\Usuario\miniconda3\Scripts;C:\Users\Usuario\miniconda3\bin;C:\Users\Usuario\miniconda3\condabin;C:\Program Files\Eclipse Adoptium\jdk-11.0.14.9-hotspot\bin;C:\Program Files (x86)\Eclipse Adoptium\jdk-8.0.312.7-hotspot\bin;C:\Program Files\Eclipse Adoptium\jdk-8.0.322.6-hotspot\bin;C:\Program Files\Eclipse Adoptium\jre-8.0.322.6-hotspot\bin;C:\Program Files\Eclipse Adoptium\jre-11.0.14.9-hotspot\bin;C:\Program Files (x86)\Eclipse Adoptium\jre-8.0.312.7-hotspot\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\AutoFirma\AutoFirma;C:\Program Files\dotnet;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Users\Usuario\AppData\Local\Microsoft\WindowsApps;C:\Users\Usuario\AppData\Local\GitHubDesktop\bin;C:\Users\Usuario\.dotnet\tools;C:\Users\Usuario\AppData\Local\Programs\MiKTeX\miktex\bin\x64;.;C:\Users\Usuario\AppData\Local\Programs\Microsoft VS Code\binafter: (foo) C:\Users\Usuario>echo %PATH%
C:\Users\Usuario\miniconda3\envs\foo;C:\Users\Usuario\miniconda3\envs\foo\Library\mingw-w64\bin;C:\Users\Usuario\miniconda3\envs\foo\Library\usr\bin;C:\Users\Usuario\miniconda3\envs\foo\Library\bin;C:\Users\Usuario\miniconda3\envs\foo\Scripts;C:\Users\Usuario\miniconda3\envs\foo\bin;C:\Users\Usuario\miniconda3\condabin;C:\Program Files\Eclipse Adoptium\jdk-11.0.14.9-hotspot\bin;C:\Program Files (x86)\Eclipse Adoptium\jdk-8.0.312.7-hotspot\bin;C:\Program Files\Eclipse Adoptium\jdk-8.0.322.6-hotspot\bin;C:\Program Files\Eclipse Adoptium\jre-8.0.322.6-hotspot\bin;C:\Program Files\Eclipse Adoptium\jre-11.0.14.9-hotspot\bin;C:\Program Files (x86)\Eclipse Adoptium\jre-8.0.312.7-hotspot\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\AutoFirma\AutoFirma;C:\Program Files\dotnet;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Users\Usuario\AppData\Local\Microsoft\WindowsApps;C:\Users\Usuario\AppData\Local\GitHubDesktop\bin;C:\Users\Usuario\.dotnet\tools;C:\Users\Usuario\AppData\Local\Programs\MiKTeX\miktex\bin\x64;.;C:\Users\Usuario\AppData\Local\Programs\Microsoft VS Code\binEdit: diff found:
|
conda-bot
added
pending::support
|
@kenodegard I believe the issue has been solved after running: conda update condaMy conda version is still the same ( Here is the output during the update in case it may be useful.
|
|
@javierttgg oh good, I see that the update bumped your conda 22.11.1 version to use a newer build (you had build 3 installed previously and now have build 4) thanks for letting us know how you resolved the issue |
3 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What happened?
In Windows, using Anaconda Prompt (miniconda3) to create a new environment, I am unable to use a newly created environment.
Following this steps:
(environment is correctly created)
Then, after activating the environment
All commands I've tried end up returning the following error:
Examples of commands that produce the previous error:
Might this be related to #12161?
Conda Details
conda infoconda listThe text was updated successfully, but these errors were encountered: