Surely you jest ? I may be out of line, I am quite new to Zope and have only made a few python products, but the nice thing I felt Acquisition.Implicit gave was a sense of being able to put a method into an environment and let it "discover" what was around it. Aquisition.Explicit I thought was where you knew specific things about your environment and wanted them from there instead of what you had brought along yourself. Matt On Sat, 09 Dec 2000, Jim Fulton wrote:
Chris Withers wrote:
morten@esol.no wrote:
That is, with a simple method, and not disabling the Acqusition class, something like self.aq_disabled('attribute') .
So kindof the inverse of using Aquisition.Explicit and using the aq_acquire method?
What you describe would be really cool...
The only workaround for now is to use calls to ac_acquire() and provide a filter function, but this doesn't help when other code that you have no control over accesses an attribute that you'd rather not have acquired :-(
I'm inclined to think that in some future version of Zope, we should switch to making explicit acquisition the norm.
Jim
-- Jim Fulton mailto:jim@digicool.com Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.org
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope ) -- Matt Halstead (PhD) Research and development VirtualSpectator http://www.virtualspectator.com ph 64-9-9136896