[Grok-dev] Grok via easy_install

Patrick Gerken do3ccqrv at googlemail.com
Tue May 12 04:16:26 EDT 2009

On Mon, May 11, 2009 at 19:55, Kevin Teague <kevin at bud.ca> wrote:

> On May 9, 5:50 pm, Patrick Gerken <do3cc... at googlemail.com> wrote:
> > Hi,
> >
> > I don't know if this is really be a bug, but atm if I try to install grok
> > via easy_install, it pull the depencies with wrong versions.
> > Should this use case be supported or not?
> >
> This is largely a drawback of easy_install, it will always grab the
> newest requirements in the 'install_requires' dependency graph. It's
> possible to pin this graph down to specific versions, but it would be
> a huge hassle, requiring every package Grok depends upon be released
> with every Grok release. It makes much more sense to have
> install_requires only be as specific as API compatability for a given
> package.
> However, if you really do want to use easy_install, it would be
> possible to take the same approach as TurboGears and BFG, and build a
> package index for each release that only contained packages in that
> specific release. It's kind of a backwards way of solving the problem
> but it works.
> Alternatively use buildout or pip :)

I don't see where buildout could ease the pain, cause the versions you pin
down there, also have to be on pypi.

The one advantage that I am aware of, is easy generation a versions.cfg with
whats currently installed in buildout. I agree that this is of value.

I have looked into the setup.py of turbogears, and they pin down the
versions. An idea could be to create a buildout recipe that creates a new
setup.py with the versions it has. This would solve the problems, no?

Best regards,



> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.zope.org/pipermail/grok-dev/attachments/20090512/16bbaf95/attachment.html 

More information about the Grok-dev mailing list