You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.
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.
The text was updated successfully, but these errors were encountered: