On Aug 14, 2009, at 9:59 PM, Jorge Vargas wrote:
> > On Fri, Aug 14, 2009 at 7:50 PM, kochhar<[email protected]> wrote: >> >> Hi all, >> > Hi, > >> I have a package repository which contains packages for pylons >> 0.9.6.1 After >> adding pylons 0.9.7 and it's dependent packages, my 0.9.6.1 >> projects stopped >> working. >> >> From looking at the requires.txt in pylons 0.9.6 egg it appears >> that pylons is >> specifying it's dependencies in the FooPackage >= x.y.z format. >> Consequently, >> when I re-create my project environments, they get newer versions >> of their >> dependencies which are not compatible with 0.9.6.1 (Notably Routes >> and WebHelpers) >> >> It seems bad practice for pylons to specify it's dependencies in the >> FooPackage>=x.y.z format; it's too easy to break something. Is >> there a way >> around this so I don't need to create separate package repositories >> for 0.9.6.1 >> and 0.9.7 > > I don't see this as bad format as a newer version is (in general a > better less buggy version) that said they are two ways of fixing this. > 1- releasing 0.9.6.2 with a setup.py that excludes the new > incompatible versions > 2- using something like pip and it's requirements.txt file to fix > such issue. Another alternative is to install both eggs with the -m (multi- version) option of easy_install, then explicitly require whatever version the app needs as early as possible during the app's initialization (like in middleware.py, or load_environment) -- Philip Jenvey --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
