> When an acquisition wrapper is formed, there always must some context
> (which is put into "aq_parent").
Well, as I can figure out this is the code that does the wrapping:
/* Crap, we've got to construct a wrapper so we can use Wrapper_findattr */
UNLESS (self=newWrapper(self, Py_None, (PyT
Lennart Regebro wrote at 2005-9-21 08:18 +0200:
> ...
>>What is the "aq_parent" that was used when wrapping the object?
>
>Eh, which one? The aq_chain of both the original aq wrapper and the
>indexableobjectrapper is correct. The aq_chain of the "outside"
>aq_wrapper is just []. Which seems exp
Dieter, my man!
> >Now, in our case, the object is an IndexableObjectWrapper, wrapping an
> >Acquisition wrapped object. So, aq_acquire will Acquicision wrap the
> >IndexableObjectWrapper, with the result that the object being used now
> >has no context!
>
> Really?
No?
>What is the "aq_par
Lennart Regebro wrote at 2005-9-19 17:38 +0200:
> ...
>aq_acquire will, if the first parameter is not an AcquisitionWrapper,
>and the third parameter is not None, wrap the object.
>
>Now, in our case, the object is an IndexableObjectWrapper, wrapping an
>Acquisition wrapped object. So, aq_acquire w
You know you are in trouble when you need to read the c-code of
Acquisition to understand a problem. :) This took me half the day to
figure out, and in fact, I still don't fully understand it.
So I need help with this.
CPS has an index, called cps_filter_sets. It's a TopicIndex, and
TopicIndexes
