Jupyter switches to C++ kernel and widgets
blog.jupyter.org
Jupyter switches to C++ kernel and widgets
1–10 of 16 posts
Re: Jupyter switches to C++ kernel and widgets
#2This isn’t a switch — ipython is still there.
This is a new lightweight option that drops some of the magic in favor of flexibility.
Re: Jupyter switches to C++ kernel and widgets
#3No, that's not the article's title (which is a reasonable one), but a very heavy-handed editorialization.
Re: Jupyter switches to C++ kernel and widgets
#4This isn’t a switch — ipython is still there. This is a new lightweight option that drops some of the magic in favor of flexibility.
I don't think the big news of the article is the Python kernel, but rather the C++ library that makes writing other kernels easier.
Re: Jupyter switches to C++ kernel and widgets
#5Nice - I think we will make the switch to this.
We wrote a Common Lisp kernel for Clasp (Common Lisp system that interoperates with C++ and uses LLVM as the backend -https://github.com/clasp-developers/clasp)
We implemented ipykernel and ipywidgets in Common Lisp by translating the Python code. I think we could switch to Xeus and lower the maintenance burden and contribute to Xeus.
Re: Jupyter switches to C++ kernel and widgets
#6The title is misleading and wrong. The article is about a new library that lets you write kernels in C++.
There is however a kernel for C++ that you can try here: https://mybinder.org/v2/gh/QuantStack/xeus-cling/stable?file... if interpreted C++ is your thing :)
Re: Jupyter switches to C++ kernel and widgets
#7No, that's not the article's title (which is a reasonable one), but a very heavy-handed editorialization.
I think OP doesn’t realize Jupyter supports multiple kernels and already has a bunch, they’re just adding another.
Re: Jupyter switches to C++ kernel and widgets
#8hmm no disrespect intended but .. this line of the article jumps out .. "C++ is a good choice for a standard implementation of the protocol, it is a common denominator of most of the languages out there, it has a massive developer community and is widely adopted in the industry for performance middleware applications."
AFAIK the linking characteristics of C++ are pretty bad, since the symbols are mangled in a compiler-specific way, no?
If a small library implements a protocol for any new kernel to re-use, wouldn't it be better to use a language that results in stable external symbols, for linking ?
Re: Jupyter switches to C++ kernel and widgets
#9The title is misleading and wrong. The article is about a new library that lets you write kernels in C++. There is however a kernel for C++ that you can try here: https://mybinder.org/v2/gh/QuantStack/xeus-cling/stable?file... if interpreted C++ is your thing :)
Read the whole article. It starts by introducing xeus and xeus-cling for those who don't already know about it, then gets to the subject of the title, xeus-python, which is based on xeus and, indeed, written in C++:
Re: Jupyter switches to C++ kernel and widgets
#10hmm no disrespect intended but .. this line of the article jumps out .. "C++ is a good choice for a standard implementation of the protocol, it is a common denominator of most of the languages out there, it has a massive developer community and is widely adopted in the industry for performance middleware applications." AFAIK the linking characteristics of C++ are pretty bad, since the symbols are mangled in a compile…
> AFAIK the linking characteristics of C++ are pretty bad, since the symbols are mangled in a compiler-specific way, no?
extern "C"