[Grok-dev] Re: Defining 3rd-party eggs within a grok buildout?
Philipp von Weitershausen
philipp at weitershausen.de
Wed Jun 25 13:51:31 EDT 2008
Andreas Jung wrote:
> I am playing around with Grok and I am trying to integrate SQLAlchemy
> into a Grok app. My buildout.cfg is generated by grokproject. Where do
> you configure additional eggs (for sqlalchemy, zope.sqlalchemy?
Are they an inherent dependency of your application? In other words,
does your application import sqlalchemy, zope.sqlalchemy, etc.? If so,
you should add it to install_requires of your application's setup.py.
Next time you run bin/buildout, it will pull these in.
> The buildout->eggs option within buildout.cfg is ignored by buildout
Because buildout:eggs isn't an officially used parameter. zc.buildout
doesn't just install eggs by itself, all it does is invoke recipes.
Recipes are responsible for installing eggs. Some do more, some do just
that (e.g. zc.recipe.egg), some don't have anything to do with eggs.
If you'd like to install more eggs into your sandbox, you have two choices:
a) if they're an inherent dependency of your app, add them to
install_requires in setup.py (see above)
b) if they're just specific to the deployment of the application, but
not an inherent dependency (e.g. a WSGI middleware or something like
that), you can add it to the app:eggs parameter.
> (obviously because of the 'extends' option...how to proceed?
I don't see what this has to do with the 'extends' option.
More information about the Grok-dev