Fri Aug 16 13:11:54 CDT 2013
> I'm involved in the development of a new OpenGL-based visualization
> library in Python (https://github.com/vispy/vispy). We consider adding
> a web backend in the future, and possibly integrating it within the
> IPython notebook.
> I was wondering if you had planned, as part of the development of
> IPython 2.0, to design a kind of "standardized" way to let Python and
> words, how much IPython-specific will your protocols and interfaces
Yes and no.
Yes. I think our vision is that the IPython message spec would be
trying to design it in a way that is independent of the backend
language and can work in a variety of settings - including non-Python
kernels. We are still working on the design of all the working pieces
for this part of the spec though. Once we are further along we will
solicit feedback on the ipython-dev list.
No. We don't have any plans other than our message spec to standardize
this type of thing. It is just beyond the scope of the project.
Also, I think that if this was attempted, the result would be
extremely similar to our message spec - at least if it has the same
functionality - there is only so many ways of shoving this data over
> I imagine it would be great to let non IPython-related projects
> IPython. It would make it very easy to integrate these projects in the
> IPython notebook, and it would prevent every project from reinventing
> the wheel every time.
I agree that projects shoudn't have to re-invent the wheel. If it
turns out that our message spec isn't sufficient, to prevent this from
happening, we will change it. That will be one of the most important
tests of the design.
> IPython-dev mailing list
Brian E. Granger
Cal Poly State University, San Luis Obispo
email@example.com and firstname.lastname@example.org
More information about the IPython-dev