[z3-five] Five traversal and acquisition

[Jan-Wijbrand Kolman]

Jan-Wijbrand Kolman wrote:
> To recap this situation, if I understand correctly: The consensus is 
> that the issue as described by Walco indeed is an issue, the proposed 
> fix is indeed a fix and thus, this fix should go into Five.
> 
> I can check this fix in (since I need it ;), no problem, however, I'd 
> like to know on what branches this should be applied. I assume I would 
> apply this on both:
> 
>   http://codespeak.net/svn/z3/Five/branch/Five-1.0/
> 
> and
> 
>   http://codespeak.net/svn/z3/Five/branch/Five-1.1/
> 
> right?

Answering myself,


After discussing this with Martijn, I indeed modified traversable.py on both the 
1.0 and 1.1 branches, so that FiveTraversable does not call the traverse method 
of it's superclass anymore.

There still appear to be cases where acquisition and travering behave badly. 
These situations are unfortunatly hard to reproduce in test cases so far. I will 
keep an eye on this.


kind regards,
jw

-- 
Jan-Wijbrand Kolman
jw at infrae.com