[IPython-dev] Implementing inline images in a kernel

Fernando Perez fperez.net at gmail.com
Tue Jan 28 23:41:34 EST 2014


On Tue, Jan 28, 2014 at 6:11 PM, Doug Blank <doug.blank at gmail.com> wrote:

> Well, that is probably true in general. But Calico is a very different
> kind of beast. It doesn't run the languages independently in their own
> space... all of the languages run in the same space. They can share data
> and functions and memory, but not by marshaling between systems.


Actually, that's sort of how the %julia magics work: we initialize the
julia interpreter in-process, by dlopen'ing libjulia and then create a
julia interpreter, passing it a pointer to the underlying Python VM.  This
allows the two languages to seamlessly share data structures in-memory.

I'm not saying that you shouldn't  build your own native kernel, as there's
obviously a ton of things that should be done that way (and that's why, in
addition to %julia, there's also a real, native julia kernel as Brian
mentioned).  I just wanted to point out that language %magics in the
IPython kernel aren't limited to working out-of-process.

Cheers,

f


-- 
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20140128/25c18ff5/attachment.html>


More information about the IPython-dev mailing list