[execnet-dev] execnet-1.0.3: safer ssh-interpreter termination

holger krekel holger at merlinux.eu
Tue Jan 19 16:20:29 CET 2010


i just pushed execnet-1.0.4 because i apparently introduced a new way to 
get annoying traceback messages at process-exit.  hopefully better now. 
Python interpreter shutdowns are a "fun" thing. 

cheers,
holger

On Mon, Jan 18, 2010 at 14:32 +0100, holger krekel wrote:
> 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 remote interpreters through the 'ssh' command line binary. 
> 
> The 1.0.3 release is a minor backward compatible release with these changes: 
> 
> - refine termination: CTRL-C and gateway.exit will 
>   now try harder to interrupt remote execution.  this 
>   helps to avoid left-over ssh-processes.
> - fix read-on-non-blocking-files issue probably related to jython only:  
>   the low-level read on subprocess pipes may be non-blocking, returning 
>   less bytes than requested - so we now loop.
> - Windows/python2.4: fix bug that killing subprocesses would fail
> - make RemoteError and TimeoutError available directly on execnet namespace
> - fix some doc and test issues (thanks thm and ronny), add ssh_fileserver example
> - update internal copy of apipkg
> - always skip remote tests if no ssh specs given
> 
> More info here:
> 
>     http://codespeak.net/execnet
> 
> cheers,
> 
> holger
> -- 
> _______________________________________________
> execnet-dev mailing list
> execnet-dev at codespeak.net
> http://codespeak.net/mailman/listinfo/execnet-dev
> 

-- 



More information about the execnet-dev mailing list