Michele Petrazzo <[EMAIL PROTECTED]> wrote: >some days ago I posted here and say that python "forgot" to raise an >exception, but my code was too long for make some tries possible. >But now I can reproduce the problem into another, little, project: > >www.unipex.it/vario/wxFrameSchedule.py >www.unipex.it/vario/metamenus.py > [ ... ]
It looks like a "wx sandwich" issue to me: the exception is certainly being raised and can be caught in wxFrameSchedule.OnMbWorkHour, but OnMbWorkHour is being called from the C++ wx event loop and I'd guess that the Python exception isn't being propogated across the C++ layer back out to the default handler in the Python interpretter. Robin gave a full explanation to someone else having similar problems on wxPython-users a couple of days ago, but I'm having trouble finding that. -- \S -- [EMAIL PROTECTED] -- http://www.chaos.org.uk/~sion/ ___ | "Frankly I have no feelings towards penguins one way or the other" \X/ | -- Arthur C. Clarke her nu becomeþ se bera eadward ofdun hlæddre heafdes bæce bump bump bump
-- http://mail.python.org/mailman/listinfo/python-list
