Nested assembly packages with mr.developer - Recursive assembly

Question

I use mr.developer to check my packages from the mercury repository, but I have to do something wrong, as I have a problem with nested dependencies.

For example, if I have foowith the following

  [buildout]
  develop = .

  extensions = mr.developer
  sources = sources
  auto-checkout =
      pack1
  parts = foo

  [sources]
  pack1 = hg http://blah.com/hg/pack1

foo has a dependency on pack1, specified in setup.py as install_requires = ['pack1'],

When I start bin/buildout, everything goes smoothly, mr.developer loads package1, and foo is created without problems, since package 1 was loaded and therefore exists.

Now I have another package, bar, which lists foo as a dependency.

  [buildout]
  develop = .

  extensions = mr.developer
  sources = sources
  auto-checkout =
      foo
  parts = bar

  [sources]
  foo = hg http://blah.com/hg/foo

I also list foo as a dependency in my setup.py, doing install_requires = ['foo'], what is happening now that I don't understand.

bin/buildout, mr.developer foo, buildout.cfg, foo/. foo/setup.py pack1, .

, mr.developer 1 http://blah.com/hg/pack, foo/buildout.cfg?

, , .

Cheers,

Answer 1

, .

, buildout , . ( ) -, PyPI - ( find-links).

, . , , foo, bar, , , spam bacon, buildout .

, python, .egg. python setup.py, , setup.py, " ".

; python, , . , , , . buildout, setup.py ; .egg-info , buildout , development-eggs .

mr.developer , . Buildout , () python SCM python.

, , , [sources] auto-checkout ( ). bar → foo → pack1, foo pack1 mr.developer, , buildout .

, - , ; buildout , . python, . python, , , .