Jupiter not using conda env

Asked Aug 27 '21 at 19:45

Active Aug 27 '21 at 19:53

Viewed 53 times

I've created a Conda environment (call it test), and have Jupiter installed in my base env. Below are the steps I am running :

conda create --name test
conda activate test
conda install -c Conda-forge -c defaults [some_package]
Jupyter notebook
In a fresh notebook import [some_package]

This yields a no package named ... error; this despite the fact that I can verify the package has been installed by running conda list in the env.

I think the problem is that running Jupiter notebook after conda activate is not running python from within my new environment, but rather using the 'base' python.

Anyone know how I can fix this?

Thanks!

edited Aug 27 '21 at 19:53

asked Aug 27 '21 at 19:45

eigenfoo

Update, this seems to work if I create the env using `conda create --name test jupyter` – eigenfoo Aug 27 '21 at 19:53
install `ipykernel` in the env, launch Jupyter with **base** active, then switch kernels in the notebook – merv Aug 27 '21 at 22:13
See the duplicate - one need not install jupyter in every environment. – merv Aug 30 '21 at 00:22

Jupiter not using conda env

0 Answers0