From holger at merlinux.eu  Tue Jan 12 22:02:19 2010
From: holger at merlinux.eu (holger krekel)
Date: Tue, 12 Jan 2010 22:02:19 +0100
Subject: [execnet-dev] 1.0.3 upcoming, last orders?
Message-ID: <20100112210219.GA3516@trillke.net>

Hi all,

quite likely i do a minor execnet bug fix release the next days, 
mostly some doc and improved ssh-termination-on-ctrl-C handling.
Any last orders? :)

Btw, for me execnet is a "heart" project and you are welcome
to send any issues, wishes or feedback how you are using it.

cheers,
holger


From holger at merlinux.eu  Mon Jan 18 14:32:08 2010
From: holger at merlinux.eu (holger krekel)
Date: Mon, 18 Jan 2010 14:32:08 +0100
Subject: [execnet-dev] execnet-1.0.3: safer ssh-interpreter termination
Message-ID: <20100118133208.GI30119@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 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
-- 


From holger at merlinux.eu  Tue Jan 19 16:20:29 2010
From: holger at merlinux.eu (holger krekel)
Date: Tue, 19 Jan 2010 16:20:29 +0100
Subject: [execnet-dev] execnet-1.0.3: safer ssh-interpreter termination
In-Reply-To: <20100118133208.GI30119@trillke.net>
References: <20100118133208.GI30119@trillke.net>
Message-ID: <20100119152029.GS30119@trillke.net>


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
> 

--