[Distutils] [buildout] including optional python packages for testing

[Benji York]

On Fri, Feb 18, 2011 at 4:07 AM, Chris Withers <chris at simplistix.co.uk> wrote:
> Hi All,
>
> I'm using buildout to develop a package that uses sqlalchemy and
> sqlalchemy-migrate.
>
> As a result, I'd like to test with various real database drivers; mysql,
> postgres, etc.
>
> However, I don't want to force anyone who wants to check out and run the
> tests to have all supported database drivers available and compiled.
>
> So, I'm looking for some way of specifying "optional eggs" when running the
> buildout, and not in buildout.cfg so they don't accidentally get checked in.

If I'm understanding you correctly, buildout's "install" command might
help you.

You can run bin/buildout install foo, where "foo" is a part to install.
It is not required that "foo" be listed in the [buildout] "parts ="
line.  Therefore you can have buildout actions that aren't run by
default but that you can trigger as needed.
-- 
Benji York