Am 16.02.2009 um 13:08 schrieb Jens Vagelpohl: > I'm wondering, ist it necessary to declare a dependency where we know > that it is a required dependency for another dependency we already > declare? Specifically, if CMFDefault is declared as dependency, is it > necessary to also declare CMFCore because we know CMFDefault already > declares it?
hm, do we always *know* that? Unless dealing with known behemoths aka Zope2, I'd go with explicit is better than implicit and expect declarations for any import statement. Then again I'm still not convinced that the CMF itself isn't a mini- behemoth to be eaten tail, toenails and all. Charlie -- Charlie Clark Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-938-5360 GSM: +49-178-782-6226 _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
