Open nick-youngblut opened 6 years ago
The simple fix was to restart all of the Jupyter notebook servers. I still don't see why a new conda install (with nb_conda installed in it) would affect Jupyter notebooks servers running from a different conda install. At least it was relatively easy to fix.
Maybe related to this bug: Anaconda-platform/nb_conda_kernels#73? (Open pull request with fix at Anaconda-Platform/nb_conda_kernels#79 )
I say that because of the lines
FileNotFoundError: [Errno 2] No such file or directory
[E 13:45:08.273 NotebookApp] [nb_conda_kernels] couldn't call conda:
My research lab and I use a centralized install of miniconda (not installed via root). We've been using conda <v4.4 due to issues with installing certain software for conda >=4.4. In order to start the transition to >4.4, I created a 2nd centralized install of miniconda. Installing this 2nd version of conda seems to have broken nb_conda for all of our Jupyter notebooks. For creating new notebooks, we now only have two options: "Python 3" or "R". Previously, we could select from ~15 different conda environments. When I click on the "conda" table in Jupyter, I get an error, and this is reported on the command line:
Why did a 2nd conda install affect nb_conda? Isn't everything contained in the conda install directory? Any ideas on how I revert back? Our whole research group of ~20 people now do not have access to the conda environments in Jupyter.