standard_error_message manipulation
Hi, As part of a large python product I wanted to modify the normal "Zope Error" standard_error_message page. Most exceptions will be caught in the code, and therefore those that do get through and cause an error message to be displayed to the user probably indicate a bug in our code. I would like to give the user the ability to submit the details of the exception along with their own information as a bug report. I created my own standard_error_message, and wanted it to contain a form with the values of error_value and error_tb among others. It however appears that the values of these variables get rendered into HTML much earlier than desired and therefore aren't very readable in a bug report. Is there a better approach to this problem? or a work around? thanks -d -- Dyon Balding <dyon@devcoder.com.au>
I run error_value through a simple python script to get the original message back again :) Cheers. -- Andy McKay. ----- Original Message ----- From: "Dyon Balding" <dyon@devcoder.com.au> To: <zope-dev@zope.org> Sent: Monday, April 09, 2001 9:44 PM Subject: [Zope-dev] standard_error_message manipulation
Hi,
As part of a large python product I wanted to modify the normal "Zope Error" standard_error_message page.
Most exceptions will be caught in the code, and therefore those that do get through and cause an error message to be displayed to the user probably indicate a bug in our code. I would like to give the user the ability to submit the details of the exception along with their own information as a bug report.
I created my own standard_error_message, and wanted it to contain a form with the values of error_value and error_tb among others. It however appears that the values of these variables get rendered into HTML much earlier than desired and therefore aren't very readable in a bug report.
Is there a better approach to this problem? or a work around?
thanks -d
-- Dyon Balding <dyon@devcoder.com.au>
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
argh! that wasn't the answer i was looking for :) -d On Mon, Apr 09, 2001 at 09:57:36PM -0700, Andy McKay wrote:
I run error_value through a simple python script to get the original message back again :)
Cheers. -- Andy McKay.
----- Original Message ----- From: "Dyon Balding" <dyon@devcoder.com.au> To: <zope-dev@zope.org> Sent: Monday, April 09, 2001 9:44 PM Subject: [Zope-dev] standard_error_message manipulation
Hi,
As part of a large python product I wanted to modify the normal "Zope Error" standard_error_message page.
Most exceptions will be caught in the code, and therefore those that do get through and cause an error message to be displayed to the user probably indicate a bug in our code. I would like to give the user the ability to submit the details of the exception along with their own information as a bug report.
I created my own standard_error_message, and wanted it to contain a form with the values of error_value and error_tb among others. It however appears that the values of these variables get rendered into HTML much earlier than desired and therefore aren't very readable in a bug report.
Is there a better approach to this problem? or a work around?
thanks -d
-- Dyon Balding <dyon@devcoder.com.au>
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
-- Dyon Balding <dyon@devcoder.com.au>
Sorry what answer would you like? :) Cheers. -- Andy McKay. ----- Original Message ----- From: "Dyon Balding" <dyon@devcoder.com.au> To: "Andy McKay" <andym@ActiveState.com> Cc: "Dyon Balding" <dyon@devcoder.com.au>; <zope-dev@zope.org> Sent: Monday, April 09, 2001 9:57 PM Subject: Re: [Zope-dev] standard_error_message manipulation
argh! that wasn't the answer i was looking for :)
-d
On Mon, Apr 09, 2001 at 09:57:36PM -0700, Andy McKay wrote:
I run error_value through a simple python script to get the original message back again :)
Cheers. -- Andy McKay.
----- Original Message ----- From: "Dyon Balding" <dyon@devcoder.com.au> To: <zope-dev@zope.org> Sent: Monday, April 09, 2001 9:44 PM Subject: [Zope-dev] standard_error_message manipulation
Hi,
As part of a large python product I wanted to modify the normal "Zope Error" standard_error_message page.
Most exceptions will be caught in the code, and therefore those that do get through and cause an error message to be displayed to the user probably indicate a bug in our code. I would like to give the user the ability to submit the details of the exception along with their own information as a bug report.
I created my own standard_error_message, and wanted it to contain a form with the values of error_value and error_tb among others. It however appears that the values of these variables get rendered into HTML much earlier than desired and therefore aren't very readable in a bug report.
Is there a better approach to this problem? or a work around?
thanks -d
-- Dyon Balding <dyon@devcoder.com.au>
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
-- Dyon Balding <dyon@devcoder.com.au>
participants (2)
-
Andy McKay -
Dyon Balding