Re: The code that could not be...

2006-06-22 Thread Alex A. Naanou
Steven Bethard wrote: > Alex A. Naanou wrote: > > The object's __dict__ can only be a dict derivative and at that none of > > the Python's mapping API will be used (the dict is accessed directly). > [snip] > > I wrote a patch some time back, it appears rather stable and is being > > production tes

Re: The code that could not be...

2006-06-22 Thread Alex A. Naanou
Fredrik Lundh wrote: > Alex A. Naanou wrote: > > > To mention several tasks that can be made trivial using this technique > > are, for instance zope-like acquisitions, various ACLs, interfaces and > > other namespace manipulation patterns. > > eh ? why not use Python's OO mechanisms for this, lik

Re: The code that could not be...

2006-06-22 Thread Fredrik Lundh
Alex A. Naanou wrote: > To mention several tasks that can be made trivial using this technique > are, for instance zope-like acquisitions, various ACLs, interfaces and > other namespace manipulation patterns. eh ? why not use Python's OO mechanisms for this, like everyone else is doing... --

Re: The code that could not be...

2006-06-22 Thread Steven Bethard
Alex A. Naanou wrote: > The object's __dict__ can only be a dict derivative and at that none of > the Python's mapping API will be used (the dict is accessed directly). [snip] > I wrote a patch some time back, it appears rather stable and is being > production tested. > > you can download it here: