Multiprocessing vs. [Pyro, RPyC]

[Jeffrey Barish]

With the release of multiprocessing in Python 2.6, is there any reason to
use Pyro or RPyC?
--
Jeffrey Barish

[sk...@pobox.com]

Jeffrey> With the release of multiprocessing in Python 2.6, is there any
Jeffrey> reason to use Pyro or RPyC?

As far as I know the multiprocessing module only works on one machine
(multi-cpu or multi-core), not across machines.

--
Skip Montanaro - sk...@pobox.com - http://smontanaro.dyndns.org/

[Jeffrey Barish]

sk...@pobox.com wrote:

>
> Jeffrey> With the release of multiprocessing in Python 2.6, is there
> any Jeffrey> reason to use Pyro or RPyC?
>
> As far as I know the multiprocessing module only works on one machine
> (multi-cpu or multi-core), not across machines.

So I thought at first, but then I saw this statement in the documentation:

It is possible to run a manager server on one machine and have clients use
it from other machines (assuming that the firewalls involved allow it).
--
Jeffrey Barish

[J Kenneth King]

Jeffrey Barish <jeff_...@earthlink.net> writes:

Depends. I don't know much about the multiprocessing module in 2.6,
but I have built a distributed application on Pyro.

Pyro has many advantages -- a query-able name server, GUI tools for
monitoring your setup, and remote agents. It is also rather simple in
comparison to other similar tools (*cough*twisted.pb*cough*). However,
it is essentially an RPC style system, so some people might not be too
comfortable with it. YMMV.