On Fri, Aug 14, 2009 at 9:59 PM, Jorge Vargas<[email protected]> 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
In the past Pylons has required the latest versions of packages but I don't know if it will be able to do so much longer. When WebHelpers 1 comes out, the Pylons dependency will have to remain at 0.6 so that people can downgrade if they're using things from the older version. Likewise, the simplejson install problems would have been easier if Pylons didn't arbitrarily exclude old versions even though they were compatible. The purpose in requiring the new versions was to make it easy to upgrade, although that doesn't seem to be a problem now because if you do a fresh install, it automatically picks the newest version even if the requirement is >= an older version. Not sure if -U also upgrades dependencies though. > 2- using something like pip and it's requirements.txt file to fix such issue. Does pip's requirements file override the requirements in setup.py, or does it lead to an incompatibility error if pip wants a version that setup.py excludes? -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
