[Grok-dev] Re: Grok 1.0 and beyond

Sebastian Ware sebastian at urbantalk.se
Sat Jan 5 05:04:17 EST 2008

5 jan 2008 kl. 02.39 skrev Martijn Faassen:

> Hello,
> On Jan 5, 2008 2:20 AM, Wichert Akkerman <wichert at wiggy.net> wrote:
>> Previously Martijn Faassen wrote:
>>> I know there are people who are in favor of easy_install over  
>>> buildout,
>>> but we'd need to see some really compelling arguments before we  
>>> consider
>>> throwing buildout overboard or trying to mix the two in some way,  
>>> given
>>> that buildout is already a working solution right now (with a lot of
>>> recipes available).
>> Ease of use. Telling someone to run 'easy_install xyz' is a lot  
>> simpler
>> than explaining that he needs to edit src/<appname>/setup.py, being  
>> very
>> careful to not introduce any syntax errors, and run bin/buildout  
>> which
>> can take a long time.
> That isn't very compelling:
> setup.py is not in 'src/appname', it's directly in the top-level  
> directory.
> Grok's bin/buildout does not run a long time at all (after the first
> time you run grokproject). buildout.cfg is configured so it doesn't
> needlessly check the network, after all.

I am happy with setup.py, but I needed to ask on this list to get it  
going. I like the fact that you can version control setup.py and that  
it is easy to use in an automatic remote installation scenario.

Regards Sebastian

More information about the Grok-dev mailing list