pyspi [Bug 318135] Improvements to error handling
- From: "pyspi (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
- To: pyspi-list gnome org
- Subject: pyspi [Bug 318135] Improvements to error handling
- Date: Tue, 18 Jul 2006 13:29:25 +0000 (UTC)
Do not reply to this via email (we are currently unable to handle email
responses and they get discarded). You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=318135
pyspi | general | Ver: CVS HEAD
------- Comment #3 from Dave Malcolm 2006-07-18 13:29 UTC -------
Created an attachment (id=69112)
--> (http://bugzilla.gnome.org/attachment.cgi?id=69112&action=view)
Work-in-progress patch for pyspi
Here's the furthest I've got with this. This patch successfully registers an
error handler with AT-SPI, and generates SPIException instances containing as
much data as I think we can scrape, and the data appears to be correct. It's
still got lots of debug prints in it, because this stuff is hard to debug -
pyrex likes to eat exceptions :-)
Unfortunately, actually _raising_ these exceptions is awkward. We can't raise
them from inside a pyrex callback, as pyrex simply throws these away (does
pyrex have a workaround for this???)
So I've tried a couple of different ways of adding exception hooks around
places where exceptions could occur, storing the generated exception within a
global. Ideally we'd do this automatically somehow, since there are numerous
places where problems could occur.
But so far I haven't got either approach to work.
So this is further along, but not yet working.
--
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the QA contact for the bug.
You are watching the assignee for the bug.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]