On Thu, 2009-04-02 at 09:34 -0700, Nathaniel Smith wrote: > > Really what we need is to get a traceback, to see what the recursive > call is... but with the new exception handling thingummy (that I added > to make sure that control-C always works), it's getting called at the > bottom of a giant call-stack, and when it tries to call the function > that will print the traceback, it causes another maximum recursion > error. Sigh. > > I added some code to mainline that *might* succeed at printing a full > traceback here, but I can't reproduce the problem in testing myself > (either the problem with the clipboard recursing, or the problem with > the traceback failing to print). > > So it would be lovely if someone could try to either get a traceback > with mainline or else just temporarily comment out line 110 of > wimpiggy/util.py: > #sys.excepthook = gtk_main_quit_on_fatal_exception > and then trigger the clipboard bug.
Oh. Hrm. I applied the patch from changeset 4da14cdd106e5852589769b989c5bb6e4a73df7a thinking that was what you wanted to get the traceback. I can certainly try commenting out line 110 as well if you like. b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Parti-discuss mailing list [email protected] http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
