The Artima Developer Community
Sponsored Link

Python Buzz Forum
My $HOME/.buildout/default.cfg

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Baiju M

Posts: 225
Nickname: baijum81
Registered: Aug, 2004

Baiju M is a new user
My $HOME/.buildout/default.cfg Posted: May 3, 2007 12:20 AM
Reply to this message Reply

This post originated from an RSS feed registered with Python Buzz by Baiju M.
Original Post: My $HOME/.buildout/default.cfg
Feed Title: Programming life without Python(?)
Feed URL: http://baijum81.livejournal.com/data/rss
Feed Description: Programming life without Python(?)
Latest Python Buzz Posts
Latest Python Buzz Posts by Baiju M
Latest Posts From Programming life without Python(?)

Advertisement
Buildout is a tool which can used for any kind of applications, though
it is more suitable for Python based applications. Buildout is a
cool program which provides support for creating, assembling and
deploying applications, especially Python applications. You can build
applications using Buildout recipes. Recipes are Python programs
which follows a pattern to build various parts of an application. For
example, a recipe will install Python eggs and another one will
install test runner etc. Applications can be assembled from multiple
parts with different configurations. A part can be a Python egg or
any other program. Buildout make use Python eggs and so setuptools.
To install, Buildout just enter this command: easy_install zc.buildout
(Of course, you should have installed easy_install
to run this command)

I would like to share my default Buildout configuration
($HOME/.buildout/default.cfg) here:
[buildout]
newest = false
eggs-directory = /mbaiju/eggs
find-links = http://download.zope.org/distribution/


These options are available for all buildouts in my system. Sure, I
can override these options for individual buildouts. One of my
earlier post
had given hint for using simple buildouts. There, I used
"./bin/buildout -N" to run the buildout. See yourself what -N do from
help:

$ buildout --help
...
  -N

    Run in non-newest mode.  This is equivalent to the assignment 
    buildout:newest=false.  With this setting, buildout will not seek
    new distributions if installed distributions satisfy it's
    requirements. 
...


So adding "newest=false" option helps to avoid the "-N" switch.
IMO, this should be the default for buildout.

The "eggs-directory" option is really useful if you want to use
multiple buildouts from same machine, especially when developing
applications. If this option is not set each buildout will download
and store all egg dependencies in it's own folder, by default "./eggs"
directory in your buildout.

I set "find-links = http://download.zope.org/distribution/", because
my normal buildouts are Zope 3 related, and Zope 3 project place all
new eggs there. If this option is not set, buildout will fetch egg
from
Python's cheeseshop.

Read: My $HOME/.buildout/default.cfg

Topic: On Python's make/rake (one again) Previous Topic   Next Topic Topic: Projects using Zope Component Architecture

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use