But,
plone.api conventions, which are also accepted as our style guide, do
encourage declaring all dependencies:
https://ploneapi.readthedocs.org/en/latest/contribute/conventions.html?highlight=imports#declaring-dependencies
Best Regards,
Asko
PS. Just to be clear, the orginal issue by Héctor is caused by
<includeDependencies/> of z3c.autoinclude trying to explicity include
meta|configure|overrides.zcml of each direct dependency of the package.
Also, insert Godefroid's rant on z3c.autoinclude here :>
Nathan Van Gheem wrote:
FWIW, declaring all dependencies can be frustrating for those trying
to use products still with plone 3 since plone 3 uses fake eggs.
If you already depend on Products.CMFPlone or just Plone, isn't that
enough since that already depends on those other packages?
On Mon, Mar 25, 2013 at 9:51 AM, Héctor Velarde
<[email protected] <mailto:[email protected]>> wrote:
with the upcoming release of Plone 4.3 I've been trying to declare
all dependencies of our add ons on their setup.py file.
I'm having a weird conflicting configuration actions for utility
zope.i18n.interfaces.INegotiator when I include zope.i18n, as it
was the case for collective.z3cform.widgets:
http://pastie.org/7111489
https://github.com/collective/collective.z3cform.widgets/blob/master/setup.py#L61
does anybody knows how to get rid of this?
best regards!
--
Héctor Velarde
_______________________________________________
Product-Developers mailing list
[email protected]
<mailto:[email protected]>
https://lists.plone.org/mailman/listinfo/plone-product-developers
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
