[z3-five] Five traversal and acquisition

[Walco van Loon]

Hi Sidnei,


> | The NotFoundError raised by Zope 3 traversal is caught silently, then 
> | the Five's __bobo_traverse__ does an getattr and a getitem. That fails 
> | too, after which the Zope 2 traversal does the attribute lookup again. I 
> | suggest that the FiveTraversable should only do a view lookup and not 
> | call the traverse method of its superclass.
> | 
> | All tests still pass if the call to Zope 3's DefaultTraversable traverse 
> | method is removed, so I'd like to fix this in svn.
> 
> I disagree with that. Doing this effectively removes a indirection
> point which is that you can register your own ITraverser adapter for a
> specific object. I would agree (sort of) though with registering a
> default ITraverser adapter that does only view lookup instead of all
> the lookups that DefaultTraversable does.

The latter is what I meant - changing the behaviour of FiveTraversable,
the Traversable adapter that Five registers. 

Removing the call to DefaultTraversable.traverse doesn't effect the
possibility to register ITraverser adapters AFAICS, as the ITraverser
adapter lookup in Five's __bobo_traverse__ method remains unchanged. 

Cheers,
Walco