I have just created a new env with python 3.5 using anaconda (called it python35). My root env points to python 2.7.11. I cant seem to launch ipython with this new env, here is
I could confirm the solution above (basically install notebook in active environment) in my case. Two updates from my side:
Since Anaconda 4.4 (?) ipython notebook is now jupyter notebook. So I had to install jupyter instead. I guess, deactivate and activate was required afterwards to get the path variables in notebook updated -> checked by python -c "import sys; print(sys.path)" or corresponding command in notebook.
If you aren't using a isolated anaconda environment, you may eventual calling the notebook package from your native OS-Python installation, instead the desired from Anaconda. Similarly, I had trouble with cmake or cxx, when I try to compile in Anaconda Environment - the diffent root folder might found in linux bash with e.g "which jupyter"
An addition to Andrey Sobolev solution,you should switch to conda install ipython
for higher python3.x version and log out the environment by Ctrl+D
or conda deactivate
then activate again
AFAIK, different environments in anaconda (and in venv as well) are activated by prepending env path to $PATH
environment variable. It means, that if some file (eg, ipython
) is not found in env path (the first entry of $PATH
), the system searches for it in consequent entries of $PATH
and finds it in root environment (that stays in $PATH
). To fix the behavior, you need to install its own copy of ipython
to anaconda env:
source activate python35
(or simply activate python35
, depending on the OS)conda install ipython-notebook