On 5/10/10 10:27 , kiorky wrote: > 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, but you don't need to here. A standard version pin should be suffucient. Wichert. _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
