An error occurred fetching the project authors.
- 17 Nov, 2012 1 commit
-
-
Jim Fulton authored
-
- 03 Sep, 2012 1 commit
-
-
Jim Fulton authored
Sort dict-based data for consistent output.
-
- 21 Aug, 2012 1 commit
-
-
Marius Gedminas authored
If the test happened to write to mkdir.py twice in the same second, Python's import cache wouldn't notice that the .pyc file is stale and would execute old code.
-
- 11 Jun, 2012 1 commit
-
-
Jim Fulton authored
-
- 13 May, 2012 1 commit
-
-
Jim Fulton authored
paths to set up a custom interpreter part that has the distributions or parts in the path. For example:: python bootstrap.py init BeautifulSoup
-
- 12 May, 2012 3 commits
-
-
Jim Fulton authored
both from command line and from config files. Cherry-picked from svn trunk. Thanks Godefroid.
-
Jim Fulton authored
-
Jim Fulton authored
Cherry-picked from trunk. Thanks Gary.
-
- 28 Apr, 2012 1 commit
-
-
Jim Fulton authored
-
- 15 Apr, 2012 1 commit
-
-
Jim Fulton authored
-
- 14 Apr, 2012 2 commits
-
-
Jim Fulton authored
debuggable.
-
Jim Fulton authored
-
- 10 Apr, 2012 1 commit
-
-
unknown authored
-
- 06 Nov, 2009 1 commit
-
-
Jim Fulton authored
-
- 26 Aug, 2009 2 commits
-
-
Jim Fulton authored
- When doing variable substitutions, you can omit the section name to refer to a variable in the same section (e.g. ${:foo}). - When doing variable substitution, you can use the special option, ``_buildout_section_name_`` to get the section name. This is most handy for getting the current section name (e.g. ${:_buildout_section_name_}). - A new special option, ``<`` allows sections to be used as macros.
-
Jim Fulton authored
refer to a variable in the same section (e.g. ${:foo}). When doing variable substitution, you can use the special option, ``_buildout_section_name_`` to get the section name. This is most handy for getting the current section name (e.g. ${:_buildout_section_name_}.
-
- 24 Jul, 2009 1 commit
-
-
Godefroid Chapelle authored
-
- 20 Jul, 2009 1 commit
-
-
Godefroid Chapelle authored
Conflicts: CHANGES.txt src/zc/buildout/buildout.py
-
- 19 Jun, 2009 1 commit
-
-
Jim Fulton authored
Also fixed some spurious failures in the bootstrap test.
-
- 17 Mar, 2009 1 commit
-
-
Jim Fulton authored
to see that a file removed by a subprocess was actually removed. Added logic to wait for the file to disappear. :/ Whitespace cleanup. (Although there are a few required trailing white spaces in buildout.txt.
-
- 22 Jan, 2009 1 commit
-
-
Christian Theune authored
-
- 14 Aug, 2008 1 commit
-
-
Chris Withers authored
-
- 13 Aug, 2008 1 commit
-
-
Chris Withers authored
docs for find-links, I'm not 100% on the order of location searching but hopefully someone can review...
-
- 19 Jul, 2008 1 commit
-
-
Jim Fulton authored
errors) even without the -D option. - pyc and pyo files are regenerated for installed eggs so that the stored path in code objects matches the the install location.
-
- 12 Jun, 2008 1 commit
-
-
Stefan Eletzhofer authored
https://bugs.launchpad.net/zc.buildout/+bug/239212 is indeed solved in trunk - fixed the test for the += -= syntax change.
-
- 07 Jun, 2008 1 commit
-
-
Tarek Ziad authored
-
- 06 Jun, 2008 1 commit
-
-
Malthe Borch authored
-
- 13 May, 2008 1 commit
-
-
svn+ssh://andreasjung@svn.zope.org/repos/main/zc.buildout/branches/ajung-socket-timeoutAndreas Jung authored
- 1.0.2 release
-
- 12 Feb, 2008 1 commit
-
-
Martijn Pieters authored
Remove gibberish paragraph from variable substitution section (was this ever true?), correct next paragraph to reflect current example.
-
- 29 Oct, 2007 1 commit
-
-
Amos Latteier authored
Now there's a buildout option (use-dependency-links) that allows you to disable setuptool dependency_links metadata.
-
- 20 Aug, 2007 3 commits
-
-
Jim Fulton authored
existing buildouts. Use:: [buildout] prefer-final = true to get the new policy. The new policy will go into effect in buildout 2.
-
Jim Fulton authored
both final and non-final versions satisfy a requirement, then the final version will be used even if it is older. The normal way to override this for specific packages is to specifically require a non-final version, either specifically or via a lower bound. - There is a buildout prefer-final version that can be used with a value of "false":: prefer-final = false To prefer newer versions, regardless of whether or not they are final, buildout-wide.
-
Jim Fulton authored
to work with recent change changes to use expanduser rather than reading $HOME directly.
-
- 10 Aug, 2007 1 commit
-
-
Fred Drake authored
-
- 19 Jun, 2007 1 commit
-
-
Jim Fulton authored
-
- 30 May, 2007 1 commit
-
-
Jim Fulton authored
zc.buildout logger. This reduces noise in the output. This change was so far reaching, I decided to go ahead and clean up lots of log messages, adding some missing periods and adding quotes around requirement strings and file paths. in easy_install.py, added logging to show why distributions are added in verbose mode and removed recusive code to show requirement chains when errors occurred.
-
- 12 May, 2007 1 commit
-
-
Jim Fulton authored
an empty configuration file and then bootstraps. - Except when using the new init command, it is now an error to run buildout without a configuration file. - 75607: buildout should not run if it creates an empty buildout.cfg
-
- 09 May, 2007 1 commit
-
-
Jim Fulton authored
api to help clean up created paths when errors occir in recipe install and update methods. Made sure buildout exited with a non-zeo exit status when errors occurred.
-
- 07 May, 2007 1 commit
-
-
- 14 Mar, 2007 1 commit
-
-
Jim Fulton authored
to avoid database corruption when a user breaks out of a buildout with control-c. - Don't save an installed database if there are no installed parts or develop egg links.
-