How hard would it be to use xeus-python in terminal IPython ?

[Carreau]

Hi all,

I do understand that the question I'm going to ask is not the primary goal of xeus-Python, but here me out.

I'm wondering if terminal IPython can sorta use xeus-python as its provider for exec, and have all the communications channels open but not connected to any clients yet. The idea being that you could at some point decide that you want to migrate" your terminal session to the notebook.

[SylvainCorlay]

Hey @Carreau that sounds like an interesting idea.

Trying to paraphrase: we want an in-process interactive shell, that also provides open ports for kernel connection?

[SylvainCorlay]

I think this would be doable. Actually, the internal interactive shell could use in-process zmq sockets.

For it to provide jupyter console - style features we would probably need an implementation of the jupyter console in C++ - unless there is a means to expose the standard python shell.

[Carreau]

I think this would be doable. Actually, the internal interactive shell could use in-process zmq sockets.

Well, but if we do that, then some things will be lost like the ability of a subprocess to take over the pty, an I mistaken ?

basically I want to advantage of IPython without the drawback of jupyter console while in the terminal, but I'm fine being limited to Python.