On 26-08-11 04:20, Matthew Brett wrote:
What we would very much like to do, is to be able to specify the
missing install_requires for this package (and for others we are thinking of working with)
The solution is quite simple: just add numpy to the list of eggs like this:
[mypy] recipe = zc.recipe.egg:script eggs = nibabel numpy interpreter = py That doesn't work for me. Rightly or wrongly I am guessing that the problem is that the dependency is not for the interpreter, but for running nibabel setup.py. In any case the failure remains with that addition:
Updating nibabel-target. Traceback (most recent call last): File "/tmp/tmpnKAmK6", line 11, in<module> execfile('/home/mb312/tmp/buildbotting/src/nibabel/setup.py') File "/home/mb312/tmp/buildbotting/src/nibabel/setup.py", line 40, in<module> package_check('numpy', NUMPY_MIN_VERSION) File "/home/mb312/tmp/buildbotting/src/nibabel/nisext/sexts.py", line 122, in package_check raise RuntimeError(msgs['missing'] % pkg_name) RuntimeError: Cannot import package "numpy" - is it installed? While: Updating nibabel-target.
"Updating nibabel-target": that's not the same part as that "mypy" target. Note that such an eggs attribute is only valid for that one part. So "[nibabel-target]" also should have an eggs attribute with numpy in it. Perhaps handier: add an "eggs" attribute to [buildout] with nibabel and numpy in it and use that: [buildout] .... eggs = nibabel numpy [mypy] ... eggs = ${buildout:eggs} ... [nibabel] ... eggs = ${buildout:eggs} ... DOes that work? Reinout -- Reinout van Rees http://reinout.vanrees.org/ reinout@vanrees.org http://www.nelen-schuurmans.nl/ "If you're not sure what to do, make something. -- Paul Graham"