Ipython With Different Env (using Anaconda)
Solution 1:
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:
- In command prompt, activate the environment:
source activate python35
(or simplyactivate python35
, depending on the OS) - While in environment, issue the command
conda install ipython-notebook
Solution 2:
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
Solution 3:
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"
Post a Comment for "Ipython With Different Env (using Anaconda)"