buildout/setuptools setup_requires and test_requires
Wichert Akkerman wrote:
Previously Chris Withers wrote:
Wichert Akkerman wrote:
BUT, one thing I have noticed so far is that after running buildout, I end up with eggs for Paste, PasteDeploy and PasteScript in pylons_buildout/myproject, which is wrong. Everything in setup_requires and test_requires is installed there, Why?
and buildout can't prevent that. Again, why?
setuptools internals do that, and buildout has no influence over that as far as I know. If you want to discuss that distutils-sig is the right list.
Sorry, still not sure I follow you... Are you saying that any packages specified in setup_requires and test_requires will be installed in the path of the package that specified them rather than the same location as all other eggs? If so, that would seem to be a bug, no? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Chris Withers wrote:
Sorry, still not sure I follow you... Are you saying that any packages specified in setup_requires and test_requires will be installed in the path of the package that specified them rather than the same location as all other eggs?
If so, that would seem to be a bug, no?
Nope, a feature. Packages needed -only- for packaging (setup_requires) and testing (test_requires) should not be generally installed. They are installed in a special place for use just during those particular phases of operation. No need to have them around in production. -Jeff
Jeff Rush wrote:
Packages needed -only- for packaging (setup_requires) and testing (test_requires) should not be generally installed. They are installed in a special place for use just during those particular phases of operation. No need to have them around in production.
Hmm, now I know why no-one uses setup_requires or test_requires... This is not a clear cut issue. I can see why people might feel as you do, but I belong to the other camp of people who believe that all eggs belong in one place... I guess I'll move those packages either to install_requires or extras_require['test'] and be done with it. cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (2)
-
Chris Withers -
Jeff Rush