Buildout extension to automatically develop eggs found in specified directories.

Autodevelop buildout extension

This package provides a buildout extension for automatically developing source eggs in the current project.

You might also want to look at mr.developer which does a similar job but also manages your SCM interactions, which autodevelop explicitly does NOT do.

[buildout]
extensions = isotoma.buildout.autodevelop

By default this will check every directory below where you execute buildout for setup.py. Buildout managed directories like develop-eggs-directory will be excluded. If you want to further restrict the search path, you can till the extension where to search:

[buildout]
extensions = isotoma.buildout.autodevelop
autodevelop =
src
externals

This will develop any source eggs contained in your src and externals directories.

Testing ‘real’ eggs automatically

We package all our eggs and deploy from a local PyPI mirror. It’s useful to be able to automatically run the egg build and test the buildout with that egg, rather than the checkout. You will flush out your MANIFEST problems if you make use of this.

You need to put the extension into ‘localeggs’ mode:

[buildout]
extensions = isotoma.buildout.autodevelop

[autodevelop]
mode = localeggs

0.0.11 (2011-01-23)

• buildout:directory will now be searched even if buildout:parts-directory == buildout:directory

0.0.10 (2011-08-31)

• Allow autodevelop to no-op

0.0.9 (2011-08-17)

• Remove the horrible hack from 0.0.2 ;)

0.0.8 (2011-08-16)

• Nothing changed yet.

0.0.7 (2011-08-10)

• Brown paper bag

0.0.6 (2011-08-10)

• localeggs() builds zips so that this extension is python2.4 safe

0.0.5 (2011-08-10)

• Properly deal with lists that have gaps in the middle

0.0.4 (2011-08-10)

• Add \${autodevelop:mode} which can be deploy, localeggs or checkout.

0.0.3 (2011-06-23)

• Nothing changed yet.

0.0.2 (2011-06-16)

• If there are develop eggs, we will force them to be used over pinned versions.

Project details

Uploaded source