Stephan Richter wrote:
My major concern is speed here. Any debug handling will make the registry
slower; I am using adapters very heavily in my code and any slow-down of one
lookup would be multiplied many times.
+ sys.maxint.
cheers,
Chris
--
Simplistix - Content Management, Zope Python
On Tuesday 16 January 2007 08:23, Marius Gedminas wrote:
explainAdapter is probably a bad name for this. Maybe the whole API is
bad. Maybe it would be more useful to list all adapters that could
adapt your object to the desired interface, and list them in the order
of specificness:
You can
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
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
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.
Well, you could set a list into __traceback_info__
One of the most common issues that I've faced, and watched several
people struggle with, during Zope 3 development is to figure why a
certain adapter is not found, or why a certain other adapter is found
instead of the one you are expecting.
I was wondering if there is something that could be
