[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUe-dev] Proposal: Handling of "uncaught exceptions" in forms
From: |
Johannes Vetter |
Subject: |
[GNUe-dev] Proposal: Handling of "uncaught exceptions" in forms |
Date: |
Tue, 10 Aug 2004 14:05:44 +0200 |
Hi,
At the moment uncaught exceptions are not handled by the forms-client,
meaning they're passed through and displayed on the starting shell. As
we can see in the forms/uidrivers/<driver>/ErrorHandler.py
implementations there was something like 'handleUncaughtException ()'.
But this function doesn't work for all drivers, i.e. wx
So what about the following solution:
a ui-driver can implement the function "handleUncaughtException (exType,
exValue, traceback)". If there's such a function it will be used as
exception-hook for the sys-module (sys.excepthook). The parameters of
this function are the same as returned by sys.exc_info () function.
if a ui-driver has no such support, it should *NOT* have a
'handleUncaughtException'. (like wx does by now)
Another idea would be if debug-level is greater than 0, the
handleUncaughtException could include a traceback, or otherwise just
display exception-type and message.
Suggestions and input are welcome,
Thanks,
Johannes
--
BYTEWISE Software GmbH Tel +43 (5577) 89877-0
i.A. Johannes Vetter Fax +43 (5577) 89877-66
A-6890 Lustenau, Enga 2 http://www.bytewise.at
-------------------------------------------------------
Wir bieten die Installation von Debian GNU/Linux auf
Servern für kleinere Netzwerke zum Pauschalpreis an.
Mehr dazu unter http://www.bytewise.at/texte/pl-debian
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
- [GNUe-dev] Proposal: Handling of "uncaught exceptions" in forms,
Johannes Vetter <=