As an alternative solution, I changed the owner of ~/.conda to myself: sudo chown -R $USER ~/.conda I think the root cause of the problem (at least in my case) was that ~/.conda was owned by root for some reason. Other solutions suggest making its access more permissive (open writing to the group or even … Read more
Without virtual environment or inside the environment, you can update python as follow: conda update python Or you can upgrade or downgrade the environment python version: conda install python=3.7 Updating or Upgrading Python
In a Notebook’s cell type and execute the code: import sys !{sys.executable} -m pip install –user matplotlib and reload the kernel (src: http://jakevdp.github.io/blog/2017/12/05/installing-python-packages-from-jupyter/ )
You have enum34 installed, which requires 2.6-3.5. Installing Python 3.6 is thus not possible without either updating enum34 to see if newer versions support 3.6, removing enum34, or installing Python 3.6 in a new environment.
Removing all directories inside the envs subdirectory that resides inside conda does the job. This is generally in your user folder ~. ~\.conda\envs\
No native builds available Since Python 3.8 had been released for about a year when Apple Silicon hit the market, Python 3.7 builds for osx-arm64 were never part of the regular build matrix for Conda Forge. Workaround: Emulate Immediate alternatives for using 3.7 on Apple Silicon systems would be to emulate x86_64 with Rosetta or … Read more
brew install anaconda export PATH=”/usr/local/anaconda3/bin:$PATH”
According to your error message you can’t upgrade conda base to python 3.10 since this would lead to incompatibilities. (Supposedly there are some issues with the numpy package.) So you’ll have to wait for the next Anaconda release. However, the whole point of conda is using virtual environments: conda create –name py10 python=3.10 This allows … Read more
There is a –revisions, -r flag for this. conda list –revisions Check the conda list –help for more info. If you’d like an exact history, there is a conda-meta/history log in every environment. You could, for example, pull out every command ever executed in an environment, plus a timestamp, using grep -B1 “^# cmd” ${CONDA_PREFIX}/conda-meta/history
I met the same problem a few days ago. I found the anaconda navigator will start a process called pythonw. So the following is my solution: open a cmd window; use command tasklist | findstr “pythonw” to find the pid of pythonw, like 37200; use command tskill 37200 to kill the process. By the way, … Read more