idlinds
commented
4 years ago Same issue. 2020-07 version of Anaconda running on Linux Mint Debian Edition 4 (based on Debian Buster). Two environments available, "base" and "working", the former created at installation and the latter cloned from "base" using conda create --clone. Launching Jupyter Notebook or QT Console from Anaconda Navigator always launches in "base" environment, regardless of which environment is selected in the "Applications on" drop-down.This means packages installed in "working" are not available, even though they appear correctly on the packages list for that environment. Also checked this using sys.executable to obtain path to current Python interpreter. This is always ~/anaconda3/bin/python regardless of the environment selected. Launching Jupyter Notebook or QT Console directly from a terminal session with the appropriate environment activated shows correct behaviour: packages in that environment can be imported and sys.executable points to ~/anaconda3/envs/working/bin/python when "working" environment is active.
juartinv
csoja
Actual Behavior
Anaconda-Navigator opens Jupyter and Spyder in the default environment regardless, of which one is currently activated. In Spyder I have to change Python interpreter in settings. In jupyter only one kernel is available, so I can force it to use different environment.
Expected Behavior
Anaconda-Navigator should start Spyder and Jupyter with interpreter matching the environment from which they are started from. If they are started from "base", "base" should be the interpreter. IF they are started from "env1", "env1" should be the interpreter.
Steps to Reproduce
Create at least one enviroment apart from "base". Try to run Spyder or Jupyter not from "base".
Operating System:
Pop_OS (Ubuntu 20.04)
conda infoconda list --show-channel-urls