On Wed, Feb 23, 2011 at 3:50 AM, Wichert Akkerman
On 2/23/11 00:12 , Chris Withers wrote:
I've experiences problems when my package specifies a setup_requires="PasteScript" in it's call to setuptools' setup function when using buildout and my package is specified as a develop egg in the buildout.
I was doing this to avoid the following:
/usr/local/lib/python2.6/distutils/dist.py:266: UserWarning: Unknown distribution option: 'paster_plugins'
..but specifying setup_requires as above seems to:
- install the PasteScript and Paste eggs directory in the checkout of my package under development (not ideal)
- trip up buildout into thinking that those packages are globally available and so not install them (really bad...)
- cause zc.recipe.egg, as a result, to not install scripts from those packages even when dependent-scripts is specified as true.
Worse still, because buildout doesn't seem to know much about those packages, even when the setup_requires line is removed, the .egg folders in the development checkout of my package still cause the above buildout problems.
Has anyone else experienced this?
As far as I know zc.buildout is not capable of handling setup_requires and test_requires (and hence the abuse of extra_requires for test requirements).
I'd like buildout to support setup_requires. I've heard at times that it works and at others that it doesn't. I doubt there are tests for it. tests_requires can't be supported by buildout (testrunner recipes) because it's invisible to buildout. It's not included in the meta data that buildout can see. (Or at least it wasn't before. Perhaps distribute fixes this.)
Where's best to report this?
The obvious place is the buildout bug tracker: https://bugs.launchpad.net/zc.buildout/+filebug I can't say when it would be acted on, but at least it would be recorded. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton