Re: UPDATE: PyCall module to call Python functions from Julia
On Wed, Feb 20, 2013 at 7:32 PM, Rahul Dave
> Working on this as soon as I finish my ipython/nltk/pandas course this week
> (for librarians!).
Great! BTW, I'll be giving a talk at MIT next Friday about IPython
(time/place TBD), if you can make it there I'd be happy to talk more
about the details there.
> First try is to basically copy the matlab magic (using the python-matlab
> bridge) to create a simple %%julia magic talking to the existing webserver
Yup. That would be useful in and of itself, as it would also let
python users use Julia as a way to speed up loopy code. I'd love to
have this also as an easy way of learning about Julia from the
comforts of code I already know well, the python side.
> The second one would be to use Avik's zmq2 module to communicate directly
> with the tornado front end.
> The third one would be (once the notebook js/css is refactored according to
> the roadmap you guys posted) to communicate directly with julia using the
> websockets protocol, but this is not as flexible as the second one as you
> cant mix in pythonic and R'ic and other fun.
Actually I don't think you should go to #3. The way we think about
the architecture, kernels must speak the zmq protocol
That's because the http server is a particular detail of running via
a web browser, but for example the Qt console could also be used for
Julia, and other, different web services could be built using a
different server architecture.
The protocol *is* the zmq/json layer, that's where your kernel should
sit. If you speak the protocol correctly, you'll be able to use every
compliant client, including the terminal, qt console and notebook.
I'm sure we'll find places where we've made assumptions too close to
python for this to work perfectly, but that's the point of this
exercise: to identify them and fix them so the protocol is really
> Are there any plans for any direct file editing in the notebook? RStudio has
> this very nice capability of sending stuff back and forth from the repl to
> the source and vice versa. And from history to source. Would be lovely to
> have this in the notebook....in tomorrow's course I'm finally getting to
> modules and code organization and such, and will be using a text editor. But
> a browser based one would be so good for teaching....
Yup, we know we need it. Patience, patience :)
> The notebook rocks!
Glad you like it!