Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Host kernel not detected; all others OK

See original GitHub issue

When launching jupyter notebook from a conda env running Python 3.7 and nb_conda_kernels 2.2.0, the notebook fails to identify the kernel of host environment from which Jupyter was launched. [edit: this behavior also found using Python 3.6 build in 3.6 env].

Using conda-forge::nb_conda_kernels=2.1.1=py36_1001 in a Python 3.6 env gives expected behavior: all kernels are available.

Similar problem to but I think this is different from #112.

Example 0

$ conda activate py37
$ jupyter notebook

Jupyter file browser opens; click on New py37

  • All Python 3.6 kernels available
  • R kernel available
  • My other Python 3.7 kernel (s37) available but not the host py37

Example 1

Equivalent result when I activate a different Python 3.7 env and launch jupyter notebook:

$ conda activate s37
$ jupyter notebook


The py37 env from the previous example is visible and operable. py37_version

Versions (both 3.7 envs)

nb_conda_kernels          2.2.0                 py37_1000    conda-forge
jupyter                   1.0.0                      py_1    conda-forge
jupyter_client            5.2.3                      py_1    conda-forge
jupyter_console           6.0.0                      py_0    conda-forge
jupyter_core              4.4.0                      py_0    conda-forge 
python                    3.7.0                h4eca856_1    conda-forge
conda info --all
conda info --all                                                   14:49:02

     active environment : None
            shell level : 0
       user config file : /Users/ralexx/.condarc
 populated config files : /Users/ralexx/.condarc
          conda version : 4.5.11
    conda-build version : 3.16.2
         python version :
       base environment : /usr/local/share/anaconda  (writable)
           channel URLs :
          package cache : /usr/local/share/anaconda/pkgs
       envs directories : /usr/local/share/anaconda/envs
               platform : osx-64
             user-agent : conda/4.5.11 requests/2.19.1 CPython/3.7.1 Darwin/16.7.0 OSX/10.12.6
                UID:GID : 501:20
             netrc file : None
           offline mode : False

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:7

github_iconTop GitHub Comments

mcg1969commented, Nov 24, 2018

Indeed, I think y’all are right—the duplication in the kernel list is better than the confusion. We can even, say, put some sort of indicator into the format noting the current environment. I’m open to a PR on this, and at some point I’ll take a look.

marabout2015commented, Feb 13, 2019

I would have been a big time saver to include this change of behavior in the list of breaking changes. I know multiple people beside myself who have been scratching their heads over this bug. The sooner you can push the new version the better.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Conda environments not detected · Issue #112 - GitHub
Kernels all detected and available!! Even when I put the file back exactly as it was, I can create new environments and they...
Read more >
How to Fix VirtualBox "Kernel Driver Not Installed (rc - YouTube
Kernel driver not installed, is the most popular error users will get while using VirtualBox. Luckily, it easy to resolve in system ...
Read more >
Setting Up KDNET Network Kernel Debugging Manually
On the host computer, open WinDbg. On the File menu, choose Kernel Debug. In the Kernel Debugging dialog box, open the Net tab....
Read more >
Conda environments not showing up in Jupyter Notebook
This is the best answer as of Jan 2018. Jupyter should auto-discover your kernel on startup if you simply conda install ipykernel inside...
Read more >
Dell Latitude 5510 No network interface found! Kernel might ...
Im getting this message when im trying to upload. “No Network Interface found, your kernel is most probably missing the correct driver!
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found