albert boulanger wrote:
> 
>      You should be able to make "standard_error_message"s that
>      do not generate secondary errors.
>      If you fail, a crude minimal error handling should be okay
>      as a last resort.
> 
> The Lisp system on Symbolics had both. It had a too-many-error-frame
> detector for the error reporter that used a crude system when
> triggered. It would be nice that the crude error messages be settable
> in a way that is hardended, perhaps env vars?

I like the idea of a text file for these, rather than being embedded in
the python source. Surely that can't be too hard?
(Squishdot does this already for some things ;-)

cheers,

Chris

_______________________________________________
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )

Reply via email to