Le 10/05/2010 10:05, Hedley Roos a écrit : > Hi > > I've been able to successfully avoid this problem for a while now, but > with Plone 4 looming I have to face it. > > The issue is with dependencies explicitly listed in an egg's setup.py. > As an example PloneSoftwareCenter lists Products.ArchAddOn. Not > Products.ArchAddOn<=1.5 etc but just the egg name. > > Does anyone know how to force version 1.5? And what is the best practice > for setup.py files? Should you specify a version range or not? > > > You can use minitage.recipe.* [1] [2] to resolve your problem. You can even use buildout.minitaficator[1] extension in a classical buildout without touching anything else than the extensions = setting. With minitage.recipe.[egg/scripts], the buildout version take precedence on the setup.py explicit requirement. You'll still have a warning during buildout execution explaining you that there is a VersionConflictError but it will not fail and takes the buildout version one.
[1] - http://pypi.python.org/pypi/buildout.minitagificator [2] - http://pypi.python.org/pypi/minitage.recipe.egg / http://pypi.python.org/pypi/minitage.recipe.scripts -- Cordialement, kiorky GPG Fingerprint: _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
