Buildout: Including another Python project via mercurial?

Question

I have a project called Foo/ that has buildout.cfg and setup.py. Now there is another project called Bar/ .. which too has buildout.cfg and setup.py. Since Bar/ depends on various Python modules, it has install_requires=['lxml', 'SQLAlchemy'] in its setup.py. Foo/ depends on Bar/.

But Bar/ does not have a release yet. How do I include Bar/ in Foo's buildout so that I can import Bar's modules, lxml and SQLAlchemy?

Assume that Bar/ is using mercurial as its revision control system.

My attempt: Buildout mercurial recipe does not do much. It only clones the repository, but does not automatically get the eggs for install_requires in Bar/setup.py and add Bar/ itself to sys.path.

Actual example: Here's what my buildout.cfg looks like (Bar == mercurialrecipe package):

[buildout]
parts = ... pyrtm ...
develop = . parts/pyrtm
eggs = pyrtm

[pyrtm]
recipe = mercurialrecipe
repository = http://bitbucket.org/srid/pyrtm

...

This does not work because sys.path does not contain the path to locally cloned mercurialrecipe (in parts/mr), and the dependencies (from parts/mr/setup.py) are not installed.

Answer 1

If you can check out/clone the repository, then you can develop the python module as usual:

[buildout]
...
develop = src/Bar
eggs = Bar

Answer 2

You're using mercurial recipe to make a mercurial checkout of the mercurial recipe that you want to use as a development egg.... There's a huge circular dependency in there.

Buildout needs the mercurial recipe to run the "mr" part. So it grabs the recipe from pypi. It doesn't yet know that the recipe will actually download the recipe.