Jehiah Czebotar schrieb:
Is there a reason that the WebKit/Application.py code (lines 665-705)
only handles a few specific types of errors, and doesn't enter the
error handling code for all unknown errors?
I am working on upgrading to 1.0 and i realized in testing that my
application logic
thanks for the response Christoph.
Inheriting from Exception is probably good advice, and i'll just patch
my version of webware to handle things differently as i audit my code
to make updates to exception handling.
that's probably what i get for trying to update to version 1.0
straight from a 6
Jehiah Czebotar schrieb:
I've also found that Webware/WebUtils/cgitb.py hadles non object
errors (ie: raising a string as the error) improperly causing the
'fancy traceback' to fail to display the actual traceback. Here is a
change that works for me, but i think it would be better to do enough
Is there a reason that the WebKit/Application.py code (lines 665-705)
only handles a few specific types of errors, and doesn't enter the
error handling code for all unknown errors?
I am working on upgrading to 1.0 and i realized in testing that my
application logic code that raises a custom error
