[pygtk] Takes two Ctl-C to kill?
David Ripton
dripton at ripton.net
Wed Jul 15 23:40:55 WST 2009
On 2009.07.15 09:49:01 -0500, skip at pobox.com wrote:
> We have an admittedly odd setup at work, but I thought I'd ask here first...
> If you have a multithreaded PyGtk application and kill it with Ctl-C does it
> require one or two Ctl-C's to do the deed? We are seeing two (using pygtk
> 2.12). I sort of assume we are doing something wrong, swallowing the first
> exception somehow or unwinding some inner frame. The next Ctl-C kills the
> app.
>
> We're not really concerned with trapping Ctl-C but with other more important
> exceptions being silently ignored.
Also seeing two here. Only during the part of the program's run when
two threads are active. When only one thread is active, it exits with a
single ctrl-C. CentOS 5.3, PyGTK 2.10.4
--
David Ripton dripton at ripton.net
More information about the pygtk
mailing list