I think I'm going to study some more. This is going to take a wee' bit more time before I can proceed.
On Mar 11, 2:57 pm, Gael Pasgrimaud <[email protected]> wrote: > On Thu, Mar 11, 2010 at 9:29 PM, Mike Orr <[email protected]> wrote: > > On Thu, Mar 11, 2010 at 12:03 PM, Gael Pasgrimaud <[email protected]> wrote: > >> On Thu, Mar 11, 2010 at 8:41 PM, Mike Orr <[email protected]> wrote: > >>> On Thu, Mar 11, 2010 at 10:59 AM, Gael Pasgrimaud <[email protected]> wrote: > >>>> Hi, > > >>>> On Thu, Mar 11, 2010 at 7:35 PM, gazza <[email protected]> wrote: > >>>>> Hiya, > > >>>>> I am installing on the production server and hit the below: > > >>>>> "Installed distribution Webhelpers 1.0b4 conflicts with requirement > >>>>> WebHelpers>=0.6.1,<0.6.99" > > >>>>> I guess others have seen this problem. What was the workaround? > > >>>> Try to remove the conflicted version from your file sytem and install > >>>> the correct one with easy_install > > >>>> Btw I think that fixing eggs versions in setup.py is a bad idea. > >>>> Pylons should have a pip's requirement file or something like that (I > >>>> also know Zope's Known Good Set aka KGS) for each releases to get the > >>>> correct dependencies versions. > >>>> Then if you have a fix in a dependency you can change the required > >>>> version without releasing a new Pylons versions > > >>> The problem is Paste uses entry points and 'pkg_resources.require', > >>> which blows up if any requirements are in conflict. > > >> That's why a requirement file can fix the problem if you only have > >> Dep==X.X in this file. > >> This assume that you can have a *stable* Pylons X.X environment even > >> if a broken dependency is released on pypi. > > > How does a requirements file override the version-comparing > > 'pkg_resources.require' does? It seems like requirements control only > > what gets installed, not runtime import conflicts. Does installing > > requirements actually change the egg-info metadata to allow those > > versions to be imported without errors? > > There is no overriding but if you install your pylons with a KGS it > assume that it wont conflict at runtime. At least in an virtualenv > --no-site-packages. > This also assume that you can reproduce the exact same environment in > development and production. > And last thing, it's always useful when you need to work on a old > project and already rm -Rf your dev env of this project > Pylons only have a few dependencies so it's not a real problem but > when you have worked with zope and plone projects you know that this > required in a quality process. > Btw I was thinking about that a few days ago so it will be useful at > least for myself ;) > > > > > -- > > 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 > > athttp://groups.google.com/group/pylons-discuss?hl=en.- Hide quoted text - > > - Show quoted text -- Hide quoted text - > > - Show quoted text - -- 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.
