Hi Reinout I didn't notice this topic was going on without me :) In the meantime I received help at StackOverflow: http://stackoverflow.com/questions/5703456/how-can-i-install-my-project-from-source-with-buildout. Your solution is identical to what I ended up with, except that I used the recipe z3c.recipe.scripts, because I understood that it improves on zc.recipe.egg.
Thanks, Arve On Tue, Apr 19, 2011 at 9:46 AM, Reinout van Rees <[email protected]>wrote: > On 18-04-11 16:32, Jim Fulton wrote: > >> My project (checked out from Git to be specific) comes with a >>> > Distribute-based setup.py, and I'd like to install it into an isolated >>> > Python environment. That is, the equivalent of running 'python >>> > setup.py.install' in my project directory, but into an isolated >>> environment. >>> > I was hoping I could use Buildout for this. >>> >> Your specific requirements is better matched by virtualenv. >> > > It *is* possible with buildout in case you want to experiment :-) > Put this in your buildout.cfg: > > [buildout] > develop = . > parts = scripts > > [scripts] > recipe = zc.recipe.egg > eggs = your-egg-name > > Grab a bootstrap.py, run it and run bin/buildout. > > > The one thing that, to me, still is a big advantage of buildout over > virtualenv in cases like this: you can just run the scripts in bin/* as-is. > You do not need to activate the virtualenv beforehand. > > For quick installs and try-outs I prefer virtualenv, though :-) > > > Reinout > > _______________________________________________ > Distutils-SIG maillist - [email protected] > http://mail.python.org/mailman/listinfo/distutils-sig >
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
