jupyter / jupyter/notebook

two conda envs with the same name

Open
#3,375 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
13.3k
Forks
5.8k
Avg merge
6d 11h
Merged PRs (30d)
7

Description

My research group and I are transitioning from conda <4.4 to conda >=4.4 (some bioinformatics software didn't install correctly with >=4.4), and so we have 2 miniconda installs: one running conda < 4.4 and the other running conda >4.4.

The problem is that there are conda environments in each conda install that have the same name (eg., the "py3" conda environment). When we run Jupyter, all environments for both miniconda installs are listed for creating new notebooks, and environments with the same names in both installs are not differentiated. For instance, the "py3" conda environment found in both conda installs is only shown under the "New" notebook list as "py3". So, which "py3" conda environment is it? Is it from the conda >4.4 install or the <4.4 conda install? How can I tell, besides trying to import packages that may be different between the two identically-named environments (or looking at their versions)? How do I use the "py3" conda environment from the other conda install?

I'm running Jupyter in conda 4.4.10 on Ubuntu 16.04.3. My Jupyter install info is:

```
jupyter 1.0.0 py36_0 conda-forge
jupyter_client 5.2.2 py36_0 conda-forge
jupyter_console 5.2.0 py36_0 conda-forge
jupyter_contrib_core 0.3.3 py36_1 conda-forge
jupyter_contrib_nbextensions 0.4.0 py36_0 conda-forge
jupyter_core 4.4.0 py_0 conda-forge
jupyter_highlight_selected_word 0.1.0 py36_0 conda-forge
jupyter_latex_envs 1.4.0 py36_1 conda-forge
jupyter_nbextensions_configurator 0.4.0 py36_0 conda-forge
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the duplicate environment names in Jupyter's New notebook environment list with two conda installations. Trace how available environments are discovered and labeled, then verify that identically named environments can be distinguished and selected; the issue mentions no source file or test to begin with.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook, python
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.