When using the Anaconda environment, I cannot start Jupyter to work in a laptop. I can do this without the environment, but I need to be able to use the environment. Here is what I do and I get errors:
ben@ben-K60IJ :~/surveillance_sound_classifier/surveillance_sound_classifier$ source activate EECS352 discarding /home/ben/anaconda/bin from PATH prepending /home/ben/anaconda/envs/EECS352/bin to PATH (EECS352) ben@ben-K60IJ :~/surveillance_sound_classifier/surveillance_sound_classifier$ jupyter notebook Traceback (most recent call last): File "/home/ben/anaconda/envs/EECS352/bin/jupyter-notebook", line 4, in <module> import notebook.notebookapp File "/home/ben/anaconda/envs/EECS352/lib/python2.7/site-packages/notebook/notebookapp.py", line 61, in <module> from .services.contents.manager import ContentsManager File "/home/ben/anaconda/envs/EECS352/lib/python2.7/site-packages/notebook/services/contents/manager.py", line 16, in <module> from nbformat import sign, validate, ValidationError File "/home/ben/anaconda/envs/EECS352/lib/python2.7/site-packages/nbformat/__init__.py", line 33, in <module> from .validator import validate, ValidationError File "/home/ben/anaconda/envs/EECS352/lib/python2.7/site-packages/nbformat/validator.py", line 21, in <module> raise ImportError(str(e) + verbose_msg) ImportError: No module named functools32 Jupyter notebook format depends on the jsonschema package: https://pypi.python.org/pypi/jsonschema Please install it first.
Yes, I did pip install jsonschema
and conda install jsonschema
AND pip install functools32
and conda install functools32
from inside the EECS352 environment to no avail; I get an almost identical error, except for this time, functools32
is replaced with _version
.
I reinstalled Anaconda, updated all its packages, created a new environment in the same way as I created this, and still get this error. I am using 32 bit Ubuntu 15.10. I used to use this environment without problems until about a week ago.
If this is a duplicate, indicate me the original; however, I have not yet found anything that is really relevant. The only thing that may be appropriate is that this error occurred after I modified some .conf
file because I was having problems updating my software using sudo apt-get upgrade
. I donβt remember what I did, and to which file, but if this is probably the source of this problem, I can spend some time trying to track it. Please let me know if I take my time to do this, and I will.