we stumbled over an annoyance that took a while to debug:

Writing an ITraversable, we used zope.traversing.api.traverse() in a
test to verify our code. We registered the ITraversable as an
(non-multi) adapter and ended up with a working test.

In the actual system, we found that the traversable would not be used.
After investigation we found a conditional branch in the traverse()
function which would look for a multi-adapter if a request was around,
and a regular adapter if not.

We didn't anticipate this difference and it cost us some time, so we
wonder whether this has to be the way it is, or whether this could be
changed to behave more obvious and consistent.

Christian and Wolfgang

Christian Theune · [EMAIL PROTECTED]
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1
Zope and Plone consulting and development

Attachment: signature.asc
Description: This is a digitally signed message part

Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to