[IPython-dev] Collaborative IPython frontends

W. Trevor King wking at tremily.us
Mon Jan 28 21:02:13 EST 2013

I've been browsing through the docs and source off and on over the
past few days trying to get a handle on a collaborative IPython
workflow.  There's a “collaborative scenarios” hint in
docs/source/development/messaging.txt and talk of an --existing option
in docs/source/interactive/qtconsole.txt.  It looks like the support
for the connect_info magic lives in IPython/zmq/zmqshell.py, but
support for --existing seems spotty (it's only supported by the
IPython/frontend/terminal/console/app.py, and
IPython/frontend/qt/console/qtconsoleapp.py frontends, as far as I can

Is this still a work in progress?  Is some sort of collaborative
session sharing in the pipes?  It looks like the kernel only handles
Python command execution (without notebook extensions like input cells
and Markdown rendering), so the collaborative use would only be
sharing a central, kernel-bound Python context.

My end-goal is to get some sort of recording and playback for
notebooks at the cell-action level (e.g. Markdown cell rendering,
Python cell execution, …), and it seemed like a logging “frontend”
could be attached as a collaborator to an existing notebook
frontend/kernel.  Then the log could be played back using a playback
“frontend” and viewed in a collaborating notebook.


This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20130128/85a9cfd7/attachment.sig>

More information about the IPython-dev mailing list