On Apr 10, 2013, at 9:14 AM, Sundance <[email protected]> wrote: > On 04/10/2013 04:33 PM, Aaron Meurer wrote: > >> That's a different use of signals. He's referring to the signal >> handler code in __init__.py that lets you break the code by pressing >> Ctrl-C. > > Oh! Indeed. > >> Can the solution to the other problem be extended? > > The other problem is specific to the way urwid sets up the display, so I > think not. > > The same approach -- catching and ignoring the exception -- will avoid the > crash, but the signal handler will still not be installed. > > I'm not sure how to address this issue. At a glance, I'd say that installing > the signal handler into the main thread from outside the main thread is not > going to be possible. > > Maybe the best approach would be to catch the exception when installing the > signal handler fails, display a helpful error message when that happens, and > update the documentation to explain that set_interrupt_handler() can only be > called from the main thread.
The documentation already says this. I just thought that it would fail only if the signal was actually sent. I didn't realize it would crash pudb just by setting the handler! Can you give a basic script to reproduce your error? Aaron Meurer > > This is not very satisfying, but I don't know how what else to do. > > -- S. _______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
