[IPython-dev] IPython notebook/parallel relation
MinRK
benjaminrk at gmail.com
Mon Dec 2 17:56:14 EST 2013
Sorry, this is probably too late, but I didn't notice this until now.
The gist is that IPython is a collection of tools for interactive computing.
One of the major pieces of that is abstracting the REPL over the network
with our message spec.
Once your execution is remote, it's a very short leap to have multiple
remote executions in parallel.
IPython.parallel is just basic tools for coordinating multiple remote
executions,
using the exact same messaging architecture as the notebook, etc.*
The most important piece of this that people often don't realize is that
the IPython 'engine' used in IPython.parallel is the exact same object as
the Kernel used by the Notebook.
The only difference is that its sockets connect instead of bind, which is
mostly insignificant due to zeromq magic.
* with a few extra messages that only make sense when the client is also an
interactive Python session, most significantly `apply`.
-MinRK
On Mon, Dec 2, 2013 at 9:44 AM, Jacob Vanderplas
<jakevdp at cs.washington.edu>wrote:
> Hi,
> I'm giving a lecture on IPython parallel this afternoon, and I'm
> anticipating the usual question of "why does IPython include parallel
> tools?" I know that the standard response is that IPython seeks to provide
> seamless tools for the entire life-cycle of the scientific idea, as well as
> the fact that it's a natural fit because the parallelism requires the same
> message passing as the notebook. I'd like to go into a bit more detail on
> the architecture overlap during the lecture. Are there any resources on
> that subject that I could look through and condense into a ~5 minute
> discussion?
>
> Thanks,
> Jake
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20131202/92cf483e/attachment.html>
More information about the IPython-dev
mailing list