Inheritance diagram for IPython.kernel.multienginefc:
Expose the multiengine controller over the Foolscap network protocol.
A parallel version of Python’s builtin map function.
This method applies a function to sequences of arguments. It follows the same syntax as the builtin map.
This method creates a mapper objects by calling self.mapper with no arguments and then uses that mapper to do the mapping. See the documentation of mapper for more details.
Create a mapper object that has a map method.
This method returns an object that implements the IMapper interface. This method is a factory that is used to control how the map happens.
A decorator that turns a function into a parallel function.
This can be used as:
@parallel() def f(x, y)
This causes f(0,0), f(1,1), ... to be called in parallel.
A parallelized version of Python’s builtin map.
This has a slightly different syntax than the builtin map. This is needed because we need to have keyword arguments and thus can’t use *args to capture all the sequences. Instead, they must be passed in a list or tuple.
raw_map(func, seqs) -> map(func, seqs, seqs, ...)
Most users will want to use parallel functions or the mapper and map methods for an API that follows that of the builtin map.
Adapt IMultiEngine -> ISynchronousMultiEngine -> IFCSynchronousMultiEngine.
Get the ids of the registered engines.
This method always blocks.
Foolscap interface to ISynchronousMultiEngine.
The methods in this interface are similar to those of ISynchronousMultiEngine, but their arguments and return values are pickled if they are not already simple Python types that can be send over XML-RPC.
See the documentation of ISynchronousMultiEngine and IMultiEngine for documentation about the methods.
Most methods in this interface act like the ISynchronousMultiEngine versions and can be called in blocking or non-blocking mode.