This has been fixed by changing the way response messages are handled in the gtk interface which now raise a KeyboardInterrupt exception when the application is closed or interrupt. And, by letting the KeyboardInterrupt exception percolate in the command line interface which was previously calling sys.exit(1). In both cases, the reactor can now handle the same exception consistently.
This has been fixed by changing the way response messages are handled in the gtk interface which now raise a KeyboardInterrupt exception when the application is closed or interrupt. And, by letting the KeyboardInterrupt exception percolate in the command line interface which was previously calling sys.exit(1). In both cases, the reactor can now handle the same exception consistently.