| Trees | Indices | Help |
|
|---|
|
|
A python-based Qube backend that has a PyCmdDispatcher.
It will run another python interpreter of some sort (usually a 2D or 3D app) as a child process, and interact with it via the PyCmdDispatcher.
|
|||
|
|||
tuple ([childArgs], [pyInitCmds])
|
|
||
|
|||
| pythonChildHandler.PyCmdDispatcher |
|
||
|
|||
|
|||
|
|||
|
Inherited from Inherited from |
|||
|
|||
DEFAULT_PYTHON =
|
|||
|
Inherited from |
|||
|
|||
|
Inherited from |
|||
|
|||
Function to initialize class members.
|
Determine the arguments necessary to invoke the child process. This is the main method that differentiates derived classes, and is probably the only method that will need to be overridden.
|
This is only overridden if a 3rd-party application which will be started cannot use the standard child_bootstrapper.py script. This can happen if the 3rd-party app doesn't support passing arguments to the bootstrapper.
|
Initialize a PyCmdDispatcher instance. The PyCmdDispatcher is this side of the bi-directional communication with a python interpeter running in a child process. It is the mechanism to dispatch the commands to the interpreter and handle any return values or exceptions.
|
Perform any steps necessary to initialize the working enviroment prior to beginning any agendaItem-specific steps.
|
Request an agendaItem (work) from the supervisor and do any steps necessary to perform the work.
|
Perform any steps necessary to clean up the working enviroment prior to shutting down the job instance.
|
|
|||
DEFAULT_PYTHON
|
| Trees | Indices | Help |
|
|---|
| Generated by Epydoc 3.0.1 on Mon Apr 17 10:45:06 2017 | http://epydoc.sourceforge.net |