metakernel icon indicating copy to clipboard operation
metakernel copied to clipboard

Merge Ipython and metakernel magics

Open joequant opened this issue 5 years ago • 3 comments

Right now Ipython and metakernel have separate standards for setting up magics, and this leads to maintainability issues. It would be nice if there were a way of writing one set of code that would work for both.

joequant avatar Aug 18 '20 07:08 joequant

That is true, but I think unavoidable in most circumstances. Metakernel's magics are designed to be language independent, whereas IPython's are baked into a specific language (Python). Having said that, there may be more we can do to fix individual differences. Is there something specific that you are thinking about?

dsblank avatar Aug 18 '20 09:08 dsblank

The problem is is that the language processing for the magics tends to be the same, and by having two different files, we are running into code forks where fixes for one code base aren't making it into the other.

In the worst case, we can have metakernel and Ipython have two different interface codes that call the same language processing module. Will take a look at what can be done.

joequant avatar Aug 18 '20 09:08 joequant

For reference, here is how xeus-python uses the IPython magics directly. However, they are also a Python kernel, as Doug mentioned.

blink1073 avatar Aug 18 '20 10:08 blink1073