[execnet-dev] Close remote gateway?

[Charles Solar]

I am attempting to use execnet to start remote python sessions for a testing
framework I am working on.  This framework will spawn a lot of remote
gateways since I want each test to be run on its own process, a simpler and
more clean approach imo.

Things work great for the first few tests but I have been noticing that
python interpreters are being left around.  Well not really left around, but
zombified and left for the OS to clean up.  This is undesirable since in the
course of several seconds this app could potentially spawn 20 or so python
interpreters, each one only 'alive' for about half a second.  I cannot wait
around for the OS to kill the zombies.

Is there someway I can remotely terminate a python interpreter through
execnet?

Currently, when the remote interpreter finishes his test I delete the
gateway and channel instances from the host and I was hoping that would
clean up the python instances on the remote server.  But that does not seem
to be the case.

Thanks for any guidance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/execnet-dev/attachments/20100611/c4766bf9/attachment.html>