You're not barking up the wrong tree... There are two kinds of error
handlers: page-level and server-level.
You can dynamically set the page-level error handler for each page by
error.setHandler(), or error.setFileHandler(), or
Each of these functions of the Spyce error module is documented at:
A page-level error handler handles dynamic errors that occur during page
You can also set the *default* page-level error handler in the Spyce
configuration file, so that you don't have to set it for each page, using
the pageerror option:
Finally, there are server-level errors. Those are the errors that occur
before page processing begins. One example of such an error is a script that
contains syntax errors. Those types of errors are handled by a server-level
error handler. You can set the server-level error handler in the Spyce
configuration file, using the error option:
All the best,
----- Original Message -----
From: "Ken Kinder" <ken@...>
Sent: Friday, December 05, 2003 1:49 AM
Subject: [Spyce-users] Default Error Page
> This question may sound a bit odd, but I'm looking at writing my own error
> handling page. The issue is, I only want to handle specific errors
> differently (such as being unable to connect to a database) but let most
> errors be processed by spyce's default error processor.
> The general idea being, for exceptions that are reasonable to catch but
> too system-wide to catch in individual spyce files, I want a user-friendly
> representation of that error to the user, like "Did you start the database
> server on host spam with username eggs."
> I see that /usr/share/spyce/modules/error.py handles exceptions by
> default. If I were to call that module myself, from my own error handling
> module, would there be any caveats I should be aware of? Am I barking up
> the wrong tree?