From jbauer at rubic.com Fri Feb 5 12:47:30 2010 From: jbauer at rubic.com (Jeff Bauer) Date: Fri, 05 Feb 2010 05:47:30 -0600 Subject: [execnet-dev] compatible with mod_wsgi? Message-ID: <4B6C0552.5050005@rubic.com> I'm very happy to use execnet to interface with a remote system running a very old Zope server. One question I have: Can execnet be run from within a wsgi process? Thanks. -- Jeff Bauer Rubicon, Inc. From holger at merlinux.eu Fri Feb 5 12:56:40 2010 From: holger at merlinux.eu (holger krekel) Date: Fri, 5 Feb 2010 12:56:40 +0100 Subject: [execnet-dev] compatible with mod_wsgi? In-Reply-To: <4B6C0552.5050005@rubic.com> References: <4B6C0552.5050005@rubic.com> Message-ID: <20100205115640.GA6083@trillke.net> On Fri, Feb 05, 2010 at 05:47 -0600, Jeff Bauer wrote: > I'm very happy to use execnet to interface with a remote > system running a very old Zope server. thanks for the feedback! > One question I have: Can execnet be run from within a > wsgi process? Thanks. Never tried - but if it allows to start a thread (execnet starts a receiver-thread) there should be no problem, i guess. If it works or you encounter issue please let us know. cheers, holger From holger at merlinux.eu Sun Feb 7 17:44:30 2010 From: holger at merlinux.eu (holger krekel) Date: Sun, 7 Feb 2010 17:44:30 +0100 Subject: [execnet-dev] execnet-1.0.5 released: doc & finalization fixes Message-ID: <20100207164430.GJ6083@trillke.net> execnet is a small and stable pure-python library for working with local or remote clusters of Python interpreters, with ease. It supports seamless instantiation of and interaction with remote interpreters through the 'ssh' command line tool. It supports Python 2.4-3.1, Jython-2.5.1 and pypy-c. The 1.0.5 release is a minor backward compatible release with these changes: - more care during receiver-thread finalization during interp-shutdown, should get rid of annoying and meaningless exceptions - fix glitch in ssh-fileserver example - experimentally add "setup.py test" support - will run py.test More info here: http://codespeak.net/execnet cheers, holger -- From A.G.Grozin at inp.nsk.su Tue Feb 23 08:40:35 2010 From: A.G.Grozin at inp.nsk.su (Andrey G. Grozin) Date: Tue, 23 Feb 2010 13:40:35 +0600 (NOVT) Subject: [execnet-dev] test failure if tested with niceness!=0 Message-ID: Fix attached Andrey -------------- next part -------------- ?????? ? execnet-1.0.5//testing: __init__.pyc diff -r -U1 execnet-1.0.5.orig//testing/test_xspec.py execnet-1.0.5//testing/test_xspec.py --- execnet-1.0.5.orig//testing/test_xspec.py 2009-12-11 15:05:52.000000000 +0100 +++ execnet-1.0.5//testing/test_xspec.py 2010-02-23 13:17:51.000000000 +0100 @@ -72,2 +72,4 @@ def test_popen_nice(self): + import os + localnice=os.nice(0) gw = execnet.makegateway("popen//nice=5") @@ -81,3 +83,3 @@ if remotenice is not None: - assert remotenice == 5 + assert remotenice == localnice+5 ?????? ? execnet-1.0.5//testing: test_xspec.pyc From jbauer at rubic.com Tue Feb 23 15:14:03 2010 From: jbauer at rubic.com (Jeff Bauer) Date: Tue, 23 Feb 2010 08:14:03 -0600 Subject: [execnet-dev] compatible with mod_wsgi? In-Reply-To: <20100205115640.GA6083@trillke.net> References: <4B6C0552.5050005@rubic.com> <20100205115640.GA6083@trillke.net> Message-ID: <4B83E2AB.7080204@rubic.com> Just an update. When I ran execnet from a mod_wsgi process it would execute a task and then hang. Either a problem with threading or perhaps something sent to stdout. Jeff Bauer Rubicon, Inc. On 02/05/2010 05:56 AM, holger krekel wrote: > On Fri, Feb 05, 2010 at 05:47 -0600, Jeff Bauer wrote: >> I'm very happy to use execnet to interface with a remote >> system running a very old Zope server. > > thanks for the feedback! > >> One question I have: Can execnet be run from within a >> wsgi process? Thanks. > > Never tried - but if it allows to start a thread (execnet > starts a receiver-thread) there should be no problem, i guess. > If it works or you encounter issue please let us know. > > cheers, > holger