Stop limiting (unblock) language kernels to just python

[rchiodo]

Thought it might be a good idea to only do this in the new kernel implementation (slower rollout).

But doesn't have to be just the raw kernel.

[dryprogrammer]

This might solve my issue as well. I am using functional programming Python variant Coconut as a IPython kernel extension. It's actually a transpiler, so not sure how easy it is to make the debugger run in Visual Studio Code. For syntax highlighting, I am using https://marketplace.visualstudio.com/items?itemName=Qwerp-Derp.vscode-coconut

https://coconut.readthedocs.io/en/master/DOCS.html#ipython-jupyter-support

[dryprogrammer]

@rchiodo May I check if this issue covers my use case please? Unlike https://github.com/microsoft/vscode-python/issues/5078, coconut is mostly python, with syntax highlighting accomplished by pygmentize.

dry@mbp:reuse$ jupyter kernelspec list
Available kernels:
  python37764bitbd906adb0af645938c0949c6e26eed94    /Users/dry/Library/Jupyter/kernels/python37764bitbd906adb0af645938c0949c6e26eed94
  coconut                                           /usr/local/share/jupyter/kernels/coconut
  coconut2                                          /usr/local/share/jupyter/kernels/coconut2
  coconut3                                          /usr/local/share/jupyter/kernels/coconut3
  python3                                           /usr/local/share/jupyter/kernels/python3

Thanks in advance! https://github.com/microsoft/vscode-python is really great to use. The speed, variables explorer, 1-click icons for common tasks, and so on.

[greazer]

Moving this to must fix for June.

[rchiodo]

@dryprogrammer this should solve your use case. Theoretically this should fix microsoft/vscode-python#5078 as well, although debugging and the variable explorer will only work for python code.

[IanMatthewHuff]

Validated. Obviously there is a ton of additional validation that we can do here. I plan on talking to our testing team on this. But installed and ran Julia on my box: