IMultiprocessChildPlugin

Role

Defines the basic interfaces for multiprocessed plugins.

Extensibility

In your own software, you’ll probably want to build derived classes of the IMultiprocessChildPlugin class as it is a mere interface with no specific functionality.

Your software’s plugins should then inherit your very own plugin class (itself derived from IMultiprocessChildPlugin).

Override the run method to include your code. Use the self.parent_pipe to send and receive data with the parent process or create your own communication mecanism.

Where and how to code these plugins is explained in the section about the PluginManager.

API

class yapsy.IMultiprocessChildPlugin.IMultiprocessChildPlugin(parent_pipe)

Base class for multiprocessed plugin.

run()

Override this method in your implementation

Table Of Contents

Previous topic

PluginManagerDecorator

Next topic

MultiprocessPluginProxy

This Page