The ``constraints`` module in zope.app.container seem to be usable outside a ZODB-application---ditto most of the interfaces. If we want to support a nozodb-environment, it would be nice to not have to pull in ZODB just to get these frameworky definitions. Is it package overkill to move these out to, say, zope.container? \malthe
On 2008-04-16 18:34:44 +0200, Malthe Borch <mborch@gmail.com> said:
The ``constraints`` module in zope.app.container seem to be usable outside a ZODB-application---ditto most of the interfaces.
If we want to support a nozodb-environment, it would be nice to not have to pull in ZODB just to get these frameworky definitions.
Is it package overkill to move these out to, say, zope.container?
+1 Also the container interfaces could be moved there. -- Christian Zagrodnick gocept gmbh & co. kg · forsterstrasse 29 · 06112 halle/saale www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891
Hi Christian
Betreff: [Zope-dev] Re: Splitting up zope.app.container
On 2008-04-16 18:34:44 +0200, Malthe Borch <mborch@gmail.com> said:
The ``constraints`` module in zope.app.container seem to be usable outside a ZODB-application---ditto most of the interfaces.
If we want to support a nozodb-environment, it would be nice to not have to pull in ZODB just to get these frameworky definitions.
Is it package overkill to move these out to, say, zope.container?
+1
Also the container interfaces could be moved there.
+1 Regards Roger Ineichen
-- Christian Zagrodnick
gocept gmbh & co. kg . forsterstrasse 29 . 06112 halle/saale www.gocept.com . fon. +49 345 12298894 . fax. +49 345 12298891
On 16.04.2008, at 18:34, Malthe Borch wrote:
The ``constraints`` module in zope.app.container seem to be usable outside a ZODB-application---ditto most of the interfaces.
If we want to support a nozodb-environment, it would be nice to not have to pull in ZODB just to get these frameworky definitions.
Is it package overkill to move these out to, say, zope.container?
hi malthe +1 good idea what we need most ist zope.app.container.interfaces.IContained and the proxies
\malthe
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
-- Lovely Systems, senior developer phone: +43 5572 908060, fax: +43 5572 908060-77 Schmelzhütterstraße 26a, 6850 Dornbirn, Austria skype: bernd.dorn
Bernd Dorn wrote:
On 16.04.2008, at 18:34, Malthe Borch wrote:
The ``constraints`` module in zope.app.container seem to be usable outside a ZODB-application---ditto most of the interfaces.
If we want to support a nozodb-environment, it would be nice to not have to pull in ZODB just to get these frameworky definitions.
Is it package overkill to move these out to, say, zope.container?
hi malthe
+1 good idea
what we need most ist zope.app.container.interfaces.IContained and the proxies
+1 I support this move as well. We just need to be careful not to move any content that can be persisted. Regards, Martijn P.S. Thanks for bringing up topics on the mailing list like this Malthe, I think that's a really good initiative!
participants (5)
-
Bernd Dorn -
Christian Zagrodnick -
Malthe Borch -
Martijn Faassen -
Roger Ineichen