On Sep 24, 2007, at 3:46 PM, Mike Orr wrote:
> I've been recommending workingenv, and James Gardener has started
> promoting zc.buildout.
Has he?
>
> I'd like to see one strategy laid out in the tutorials, with a link to
> the other approaches for advanced users. So the question is, which
> approach is most straightforward and reliable?
I just tried buildout for the first time; I had it install Pylons.
You end up with a result similar to that of virtualenv, though with a
different directory layout:
bin/
buildout.cfg
develop-eggs/
eggs/
parts/
With all the Pylons dependencies installed in eggs/. No local version
of setuptools gets installed like virtual-python/workingenv.
I immediately noticed the lack of paster in the bin dir. From my
quick skimming of the buildout docs it seems like it should be there,
but I didn't find an obvious way of making that happen (though I am a
total buildout newb).
I like buildout's ability to only go after the final release versions
of eggs. A number of folks (including Jim Fulton) have asked for this
feature in setuptools on distutils-sig. I think there's a chance of
it happening for setuptools 0.7, but this probably won't be for a while.
I like the fact that virtual-python/workingenv pretty much leverage
setuptools to handle the eggs, whereas buildout is managing the eggs
and their paths on its own. The python executable it creates for you
actually hardcodes all the egg paths.
James has probably played with it a lot more, so I'm curious as to
what his experience was.
--
Philip Jenvey
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
