[Distutils] Buildout: Including another Python project via mercurial?

[Sridhar Ratnakumar]

On 1/28/2010 5:47 PM, Sridhar Ratnakumar wrote:
>
>> * Use mr.developer [1] to automate this. I didn't find it very useful,
>> though,
>>    but this is closer to what you like to do using mercurialrecipe,
>> despite
>>    mr.developer looks more active and I know several developers which
>> are using
>>    it. It also has a comprehensive documentation, which
>> mercurialrecipe doesn't
>>    have!
>
> This too works. mr.developer 1.9 is buggy and I had to pin version 1.7.

It seems that I will end up choosing mr.developer. For those interested, 
here's the relevant part of my buildout.cfg that successfully uses 
mr.developer to develop an external package in hg repository:

   [buildout]
   develop = .
   parts = python scripts
   versions = versions
   extensions = mr.developer
   sources = sources
   auto-checkout = foo

   [sources]
   foo = hg https://example.com/hg/foo parts/

   [versions]
   mr.developer = 1.7 # 1.9 is buggy (issue 11)

For this to work, you have to ensure that site-packages/ does not 
already contain `foo' .. unless Jim merges Gary's branch and makes a new 
release of buildout: https://bugs.launchpad.net/zc.buildout/+bug/429383

-srid