[Python-Dev] PEP 371 Discussion (pyProcessing Module) (original) (raw)
Lisandro Dalcin dalcinl at gmail.com
Mon Jun 2 18:05:07 CEST 2008
- Previous message: [Python-Dev] PEP 371 Discussion (pyProcessing Module)
- Next message: [Python-Dev] C API for gc.enable() and gc.disable()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/31/08, Mark Hammond <mhammond at skippinet.com.au> wrote:
So it seems that maybe simply "setExecutable()" isn't the correct abstraction here, but maybe a "factory" approach, so the entire process creation mechanism can be replaced rather than just the name of the executable to spawn?
Indeed. If the spawn mechanisms (and even the connection mechanisms) were fully abstracted, then I believe that extending pyProcessing to work in clusters with something like MPI would be far easier. But perhaps I'm just dreaming...
-- Lisandro Dalcín
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC) Instituto de Desarrollo Tecnológico para la Industria Química (INTEC) Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET) PTLC - Güemes 3450, (3000) Santa Fe, Argentina Tel/Fax: +54-(0)342-451.1594
- Previous message: [Python-Dev] PEP 371 Discussion (pyProcessing Module)
- Next message: [Python-Dev] C API for gc.enable() and gc.disable()
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]