[py-dev] Keyboard interrupt causes unclean shutdown in py.test & py.execnet

[holger krekel]

Hi Simon, 

On Wed, Apr 29, 2009 at 11:08 +1000, Simon wrote:
> Hi Holger,
> 
> On 28/04/2009, at 19:05 , holger krekel holger-at-merlinux.eu |py-dev|  
> wrote:
> 
> > i meant that GUI threads need the main thread to run their
> > event loop.  With your patch execution will always run in
> > sub threads on the remote side.
> 
> Just a quick question, why does the GUIs event loop need to run in the  
> gateways main thread? I understand that all the widget initialisation  
> and event handling has to be done from the same thread, but I don't  
> understand why this can't be a created thread.

i don't know. It's something that people and web pages 
told/tell me.  I am hardly doing GUI programming myself. 
Is it maybe because only the main thread receives signals? 

did you try out remote_init_threads(1)? 
If that doesn't work for you i'd like to fix it or
apply your patch in some way. 

cheers,
holger

> Simon
> _______________________________________________
> py-dev mailing list
> py-dev at codespeak.net
> http://codespeak.net/mailman/listinfo/py-dev
> 

-- 
Metaprogramming, Python, Testing: http://tetamap.wordpress.com
Python, PyPy, pytest contracting: http://merlinux.eu