traceback with warning/error messages
JBrouwersAtProphICyDotCom at no.spam.net
Sun Jul 18 17:21:15 CEST 2004
In our particular case the warning message was not due to a bug in GTK.
The problem was that we were reusing a submenu in more than one popup
menu. But it took a while to reproduce the problem and figure that
It would be very helpful if a Python traceback could be printed along
with an error or warning message from any of the lower levels in
wxPython**. Especially if such messages are going to happen more
**) For example, instead of just printing the message, raise an
exception instead if some config option or environment variable is set.
In article <cdblrq$26h$2 at nemesis.news.tpi.pl>, Jarek Zgoda
<jzgoda at gazeta.usun.pl> wrote:
> Jean Brouwers <JBrouwersAtProphICyDotCom at no.spam.net> pisze:
> > Sporadically, a message like this one shows up in our wxPython
> > application:
> > (main.py:3182): Gtk-WARNING **: gtk_menu_attach_to_widget(): menu
> > already attached to GtkMenuItem
> > Is possible but tedious to find the cause of the message by inserting
> > print statements. Is there an easier way, e.g. a traceback in Python
> > when lower level messages occur?
> I see similar messages generated by (pure C++) wxWidgets applications,
> such as poedit, when running on Linux, so I think it's a matter of bugs
> in GTK backend implementation in wxWidgets, that propagate to wxPython.
> > PS) This is wxPython 126.96.36.199 and Python 2.3.2 on Linux.
> You will see this in 2.5.1 even more often.
More information about the Python-list