Buildout to run setup.py
Hi All, I'm new at buildout and I was wondering if it was possible to emulate a system command like "python setup.py install" in buildout. Use Case : [buildout] parts = MapFishTrunk [MapFishTrunk] recipe = infrae.subversion urls = http://www.mapfish.org/svn/mapfish/trunk/MapFish MapFish interpreter = Scripts\python There is a setup.py file a couple of levels down the directory that I would like to execute to build the eggs (and dependencies) and to store the resulting eggs in a location accessible to Scripts\python (which was generated using virtualenv). I can run Scripts/python setup.py install but I wonder if that can be done within buildout. TIA, Yves Moisan
On Sep 11, 2008, at 4:55 PM, Yves Moisan wrote:
Hi All,
I'm new at buildout and I was wondering if it was possible to emulate a system command like "python setup.py install" in buildout. Use Case :
[buildout] parts = MapFishTrunk
[MapFishTrunk] recipe = infrae.subversion urls = http://www.mapfish.org/svn/mapfish/trunk/MapFish MapFish interpreter = Scripts\python
There is a setup.py file a couple of levels down the directory that I would like to execute to build the eggs (and dependencies) and to store the resulting eggs in a location accessible to Scripts\python (which was generated using virtualenv). I can run Scripts/python setup.py install but I wonder if that can be done within buildout.
I'm not entirely sure what you're trying to do. Buildout is capable of building develop eggs from source directories. I don't think you can build regular eggs from source directories. You also want to run the setup with certain distributions in the path. There isn't support for doing that presently, although folks would find it useful. It would be possible to write a recipe that did both of these things. You would then define a part for the egg you wanted to install, where that part would use the recipe. You'd want to list that part before other parts that need that egg. Jim -- Jim Fulton Zope Corporation
I'm not entirely sure what you're trying to do.
Buildout is capable of building develop eggs from source directories. I don't think you can build regular eggs from source directories. You also want to run the setup with certain distributions in the path. There isn't support for doing that presently, although folks would find it useful.
The infrae recipe allows one do an svn co in parts/arbitrary_folder. Down in the hierarchy of checked out folders, there is a setup.py file. What I wanted to do is create a Python sandbox where to deploy those yet to be developed eggs. What I succeeded in doing now is install a virtualenv sandbox and build the eggs from the svn co using the sandbox Python. When I found out about the Infrae recipe I figured there should be a way to build the eggs from the source.
It would be possible to write a recipe that did both of these things. You would then define a part for the egg you wanted to install, where that part would use the recipe. You'd want to list that part before other parts that need that egg. Jim
I'll go hunt for a recipes tutorial :-) Thanx for your time. Yves Moisan
On Fri, Sep 12, 2008 at 2:28 PM, Yves Moisan
I'm not entirely sure what you're trying to do.
Buildout is capable of building develop eggs from source directories. I don't think you can build regular eggs from source directories. You also want to run the setup with certain distributions in the path. There isn't support for doing that presently, although folks would find it useful.
The infrae recipe allows one do an svn co in parts/arbitrary_folder. Down in the hierarchy of checked out folders, there is a setup.py file. What I wanted to do is create a Python sandbox where to deploy those yet to be developed eggs. What I succeeded in doing now is install a virtualenv sandbox and build the eggs from the svn co using the sandbox Python. When I found out about the Infrae recipe I figured there should be a way to build the eggs from the source.
Other options are: - to set up a svn bundle with those svn links and add some develop directives in the buildout that point to them or - to ask the package team to deal with a dev tag so you can use "==dev" in your buildout (like setutpools does for instance)
It would be possible to write a recipe that did both of these things. You would then define a part for the egg you wanted to install, where that part would use the recipe. You'd want to list that part before other parts that need that egg. Jim
I'll go hunt for a recipes tutorial :-) Thanx for your time.
Yves Moisan
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
-- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/
participants (3)
-
Jim Fulton -
Tarek Ziadé -
Yves Moisan