Re: [Zope-dev] __setattr__ and acquisition ( was RE: __getattr__and acquisition)

2002-06-06 Thread Leonardo Rochael Almeida
The only way I know is to put a wrapped object in a ._v_attribute, which means a volatile attribute. You can put, for instance, a wrapped self in, for instance self._v_alterEgo, this way you can do wrapped transversals thru it. How do you get a wrapped self to put there is an exercise left to

Re: [Zope-dev] __setattr__ and acquisition ( was RE: __getattr__and acquisition)

2002-06-05 Thread Shane Hathaway
Nicholas Henke (by way of Nicholas Henke ) wrote: Given the following code: I can see why access to self.thing fails in Inner::__setattr__, but the question is how do I do that -- can I not use __setattr__ and have to use a setAttr that is accessed via O.I.setAttr('help','me rhonda') ?

Re: [Zope-dev] __setattr__ and acquisition ( was RE: __getattr__and acquisition)

2002-06-05 Thread Erik A. Dahl
Yep. This is a problem for me I'm trying to find something through acquisition in my __setattr__. Self is totally unwrapped. Can anyone think of a creative solution? aq_acquire doesn't help because self is not a wrapped object. :( Can't pass in the object I want because the whole point

Re: [Zope-dev] __setattr__ and acquisition ( was RE: __getattr__and acquisition)

2002-06-05 Thread Casey Duncan
Why rely on __setattr__? Why not just create a regular setter function that can use acquisition instead of being clever? -Casey On Wed, 2002-06-05 at 15:24, Erik A. Dahl wrote: Yep. This is a problem for me I'm trying to find something through acquisition in my __setattr__. Self is