Vscode-jupyter: Run jupyter with kernel other than python

Created on 4 Apr 2019 · 6Comments · Source: microsoft/vscode-jupyter

Environment data

VS Code version: 1.32.3
Extension version (available under the Extensions sidebar): MS Python 2019.3.6352
OS and version: Ubuntu 16.04
Python version (& distribution if applicable, e.g. Anaconda): python 3.5.2 (also tried anaconda)
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A also tried conda, both failed.
Relevant/affected Python packages and their versions: jupyter 4.4.0

Expected behaviour

The notebook runs the same as it does when I run it from the browser.

Actual behaviour

The installed kernel is not found and I get errors that indicate a "straight python" kernel was used.

Steps to reproduce:

install almond.sh https://almond.sh/docs/quick-start-install
cd almond/examples and launch juptyer, % jupyter notebook plotly_scala.ipynb
copy the uri link that the notebook launch printed out
launch vscode in that directory
select the jupyter uri that the notebook launch supplied
import the plotly_scala.ipynb notebook into vscode
try executing cells until you hit the $ivy

Result: SyntaxError: invalid syntax

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Starting Microsoft Python language server.
[Info  - 8:55:50 PM] GetCurrentSearchPaths /usr/bin/python3 
[Info  - 8:55:50 PM] Python search paths:
[Info  - 8:55:50 PM]     /usr/lib/python3.5
[Info  - 8:55:50 PM]     /usr/lib/python3.5/plat-x86_64-linux-gnu
[Info  - 8:55:50 PM]     /usr/lib/python3.5/lib-dynload
[Info  - 8:55:50 PM]     /home/langley/.local/lib/python3.5/site-packages
[Info  - 8:55:50 PM]     /usr/local/lib/python3.5/dist-packages
[Info  - 8:55:50 PM]     /usr/lib/python3/dist-packages
[Info  - 8:55:50 PM] Configuration search paths:
[Info  - 8:55:50 PM]     /usr/lib/python35.zip
[Info  - 8:55:50 PM]     /usr/lib/python3.5
[Info  - 8:55:50 PM]     /usr/lib/python3.5/plat-x86_64-linux-gnu
[Info  - 8:55:50 PM]     /usr/lib/python3.5/lib-dynload
[Info  - 8:55:50 PM]     /home/langley/.local/lib/python3.5/site-packages
[Info  - 8:55:50 PM]     /usr/local/lib/python3.5/dist-packages
[Info  - 8:55:50 PM]     /usr/lib/python3/dist-packages
[Info  - 8:55:50 PM]     /usr/bin
[Info  - 8:55:51 PM] Microsoft Python Language Server version 0.2.43.0
[Info  - 8:55:51 PM] Initializing for /usr/bin/python3

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

Source

langley

👍3

Most helpful comment

@langley. Yeah, that's the case for now, even if you start an external server. I hate having to say that, as we really want to support more of the various language kernels. But we started out with a Python focus and we still are pretty locked into that for the near future. Polyglot support is coming, but it won't be right away.

IanMatthewHuff on 5 Apr 2019

👍5

All 6 comments

@langley Sorry, but as of right now this feature is only supported with Python. We are looking at supporting other languages in the future.

IanMatthewHuff on 4 Apr 2019

Ugh, bummer.

Even if I run an external jupyter notebook server? (I'll admit I'm still getting familiar with the jupyter architecture)

langley on 5 Apr 2019

IanMatthewHuff on 5 Apr 2019

👍5

Thanks @IanMatthewHuff for clarifying. I'm really looking forward to the polyglot world :+1:

langley on 5 Apr 2019

👍1

Also excited for polyglot support. Not only for data science – being able to use VSCode as a general-purpose repl in Node, Ruby, etc would be really delightful, and could make the editor a much more integral part of developers' workflows.