Missing options for setuptools develop
Couple of things. Currently there is no way to pass custom options through setuptools "develop" to distutils build_ext. What this means in practice is that you cannot do the following things: • pass the --debug flag to build_ext so as to have your module build against debug libraries. • pass any of the SWIG options through. • I'm sure there are other limitations. Because of this I ended up abandoning the swig functionality of distutils and running that as a pre distuils phase of my build scripts - it would be better If I could use it through distutils though. The show stopper is the fact I can't build against debug libraries - this means I cannot mix the --debug type builds and the develop functionality, something that seems like a logical thing to do. Is there any chance that someone could find a way to allow options to be passed through to build_ext as it is run? I'm sure its just a case of adding another option to setuptools develop and then passing it through at the relevant point. If noone wants to take it on I'm happy to write a patch if we all agree its the way to go. Thanks in advance Jamie
At 07:58 PM 6/28/2007 +0100, Jamie Kirkpatrick wrote:
Currently there is no way to pass custom options through setuptools "develop" to distutils build_ext.
Did you try this: setup.py build_ext --debug develop setuptools' build_ext command doesn't rebuild an existing extension built in the build/ directory, even when doing an --inplace build (as it does for "develop").
I agree that it would be nice to be able to pass build_ext arguments to develop. You can put build_ext options in a setup.cfg file. And, FWIW, buildout has a recipe that lets you specify custom build_ext options when creating develop eggs. Jim On Jun 28, 2007, at 2:58 PM, Jamie Kirkpatrick wrote:
Couple of things.
Currently there is no way to pass custom options through setuptools "develop" to distutils build_ext. What this means in practice is that you cannot do the following things:
• pass the --debug flag to build_ext so as to have your module build against debug libraries. • pass any of the SWIG options through. • I'm sure there are other limitations.
Because of this I ended up abandoning the swig functionality of distutils and running that as a pre distuils phase of my build scripts - it would be better If I could use it through distutils though. The show stopper is the fact I can't build against debug libraries - this means I cannot mix the --debug type builds and the develop functionality, something that seems like a logical thing to do.
Is there any chance that someone could find a way to allow options to be passed through to build_ext as it is run? I'm sure its just a case of adding another option to setuptools develop and then passing it through at the relevant point. If noone wants to take it on I'm happy to write a patch if we all agree its the way to go.
Thanks in advance
Jamie
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
Actually Jim, I've found I am able to call with options (as suggested by Phillip) if I put build_ext in the command line first. So the options do exist they just aren't very obvious - I think maybe just improving the docs would be enough. Thanks for the replies. Jamie On 2 Jul 2007, at 18:32, Jim Fulton wrote:
I agree that it would be nice to be able to pass build_ext arguments to develop.
You can put build_ext options in a setup.cfg file.
And, FWIW, buildout has a recipe that lets you specify custom build_ext options when creating develop eggs.
Jim
On Jun 28, 2007, at 2:58 PM, Jamie Kirkpatrick wrote:
Couple of things.
Currently there is no way to pass custom options through setuptools "develop" to distutils build_ext. What this means in practice is that you cannot do the following things:
• pass the --debug flag to build_ext so as to have your module build against debug libraries. • pass any of the SWIG options through. • I'm sure there are other limitations.
Because of this I ended up abandoning the swig functionality of distutils and running that as a pre distuils phase of my build scripts - it would be better If I could use it through distutils though. The show stopper is the fact I can't build against debug libraries - this means I cannot mix the --debug type builds and the develop functionality, something that seems like a logical thing to do.
Is there any chance that someone could find a way to allow options to be passed through to build_ext as it is run? I'm sure its just a case of adding another option to setuptools develop and then passing it through at the relevant point. If noone wants to take it on I'm happy to write a patch if we all agree its the way to go.
Thanks in advance
Jamie
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org
participants (3)
-
Jamie Kirkpatrick -
Jim Fulton -
Phillip J. Eby