On Thu, Apr 2, 2009 at 4:01 AM, Antoine Martin <[email protected]> wrote:
> I have hit this "maximum recursion" as well a few times.
> No idea why.
> But this never happened with 0.0.5, looks like a new bug to me.
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.
-- Nahtaniel
_______________________________________________
Parti-discuss mailing list
[email protected]
http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
