[Grok-dev] Dolmen and its releases

Souheil CHELFOUH trollfot at gmail.com
Thu Oct 22 11:14:52 EDT 2009

This is one thing. The most interesting part is that we effectively
respect the interface, providing the default, respecting the readonly,
For the __parent__ thing, i need to work on it more closely. I'll
probably return a containment proxy instead.

2009/10/22 Martin Aspeli <optilude+lists at gmail.com>:
> Souheil CHELFOUH wrote:
>> Have a look at the code itself
>> http://gitweb.dolmen-project.org/dolmen.file.git/blob/adf9207a69037e770838b35ed381ba942f6efdbf:/src/dolmen/file/property.py
> Ah, so it's like acquisition: set a __parent__ pointer on get.
> Note that this means you're effectively doing a ZODB write one very
> read, which is possibly bad for conflict errors and the like (unless
> there's some non-persistence magic in __parent__?)
> Martin
> --
> Author of `Professional Plone Development`, a book for developers who
> want to work with Plone. See http://martinaspeli.net/plone-book
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev

More information about the Grok-dev mailing list