build_requires support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Buildout |
New
|
Undecided
|
Unassigned |
Bug Description
In bug #110133 (setup.py needs code from another egg to build) the case was discussed where a setup.py of a package could not proceed because other eggs were expected to be on the python path. A mention of build_requires was made as a possible solution, though in that this would not work, as I had no control over the other package's setup.py.
This time I'm writing a package myself so I could set a build_requires to mention that cython needs to be installed before building (http://
Here's my setup.py:
from setuptools import setup # tried with plain distutils too
from distutils.extension import Extension
from Cython.Distutils import build_ext
setup(
name = "unbound",
package_dir = {'': 'src'},
packages = ['unbound'],
ext_modules=[
Extension(
],
headers=
cmdclass = {'build_ext': build_ext},
build_
install_
)
This feature, or the feature discussed in #110133 therefore appears to be needed to let buildout install packages that need special tools (such as cython, a fork of pyrex) to let themselves be installed.
For what it's worth, my work around uses hexagonit. recipe. download to fetch the Cython source and then uses iw.recipe.cmd to install it into my custom python. See the cython-src and cython-install sections in
http:// zcologia. com/sgillies/ hg/gdawg/ file/tip/ buildout. cfg