Hi,

Am Dienstag, den 16.01.2007, 20:28 +0100 schrieb Dieter Maurer:
> Sidnei da Silva wrote at 2007-1-15 17:25 -0200:
> > ...
> >The kind of info I'm looking for is something along the lines:
> >
> >  'We've tried to look up an adapter for (ISomething, ITheOther) but
> >none was found'
> >  'Found an adapter for IFoo, which is a base class for the IBar
> >interface requested. No adapter has been found for the most-specific
> >interface IBar'
> >
> >Comments?
> 
> In Zope 2, I would use "__traceback_info__" or (more likely)
> "__traceback_supplement__" and the traceback formatting
> facilities in "zExceptions.ExceptionFormatter".
> This is a very efficient way to analyse all problems that
> result in an exception -- far better than log entries.

Zope 3 has that as well. However, this only gives you the information of
the stack. It doesn't give you information created during the run of
e.g. loops, which I imagine would be interesting to create a trail of
"what did you do?" information. 


-- 
gocept gmbh & co. kg - forsterstra├če 29 - 06112 halle/saale - germany
www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

_______________________________________________
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to