Category : anaconda

Essentially what the title says. Here is a snippet from cmd: C:UsersMarc>conda activate quantum (quantum) C:UsersMarc>py Python 3.8.5 (default, Sep 3 2020, 21:29:08) [MSC v.1916 64 bit (AMD64)] :: Ana conda, Inc. on win32 Warning: This Python interpreter is in a conda environment, but the environment has not been activated. Libraries may fail to load. ..

Read more

I uninstalled and re-installed Anaconda on my Windows 64-bit while I had an Anaconda environment activated in my cmd. Now, cmd won’t open anymore, unless I launch it as administrator (restarting computer and removing Anaconda as Path variable doesn’t help). My guess is that my cmd is "blocked" now, as I didn’t do "conda deactivate" ..

Read more

I’m relatively new to python and anaconda. I’m trying to execute the anaconda python3 version from git bash on windows. $ python doesn’t give an error but the process seems stuck and it doesn’t return the prompt. Executing in both the windows and anaconda prompts works fine. E.g., in anaconda: (base) C:UsersAmanda>where python C:UsersAmandaanaconda3python.exe (base) ..

Read more

Conda commands (as example here the –version command) do not show any output in PowerShell: The $Env:Path variable in Windows PowerShell contains the following conda-specific paths: C:PROGRA~1Miniconda3;C:PROGRA~1Miniconda3Librarymingw-w64bin;C:PROGRA~1Miniconda3Libraryusrbin;C:PROGRA~1Miniconda3Librarybin;C:PROGRA~1Miniconda3Scripts whereby C:PROGRA~1 is the short-cut name for C:Program Files. Whereas actually the Anaconda Command prompt additionally contains the following entries at the beginning of the $Env:Path variable: C:PROGRA~1Miniconda3;C:PROGRA~1Miniconda3Librarymingw-w64bin;C:PROGRA~1Miniconda3Libraryusrbin;C:PROGRA~1Miniconda3Librarybin;C:PROGRA~1Miniconda3Scripts;C:PROGRA~1Miniconda3bin;C:PROGRA~1Miniconda3condabin; ..

Read more