An error occurred fetching the project authors.
- 31 Oct, 2007 1 commit
-
-
Jim Fulton authored
Added a configuration option that causes buildout to error if a version is picked. This is a nice safety belt when fixing all versions is intented, especially whan creating releases. (This already-desired feature made it easier to write the test for the bug fix below. :) Bug Fixed: When installing from source releases, a version specification (via a buildout versions section) for setuptools was ignored when deciding which setuptools to use to build an egg from the source release.
-
- 30 Oct, 2007 2 commits
-
-
Ross Patterson authored
151820: Add the distribution directory to sys.path when running the setup.py script so that the setup.py script can import modules from the distribution directory.
-
Ross Patterson authored
Fix verbose option handling of debug logging message
-
- 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.
-
- 28 Oct, 2007 1 commit
-
-
Jim Fulton authored
When using a local find links or index, distributions weren't copied to the download cache.
-
- 27 Oct, 2007 1 commit
-
-
Jim Fulton authored
-
- 20 Aug, 2007 2 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.
-
- 05 Jul, 2007 1 commit
-
-
Jim Fulton authored
for versions if the given requirement had an upper limit and we already had the distribution whos version was the upper limit. Added simpler tested code that checks for the simpler case that teh requirement is for a specific version and we already have that version. In general, specifying upper limits other than a single version is kind of dumb, so it's not worth optimizing for that case.
-
- 20 Jun, 2007 3 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
-
Jim Fulton authored
deterministic output by outputing all of standard output followed by all of standard error.
-
- 19 Jun, 2007 1 commit
-
-
Jim Fulton authored
Removed a test that was obsoleted by a setuptools improvement in handling failed downloads. Updated to reflect a change in bootstrapping. (I wonder why this wasn't needed sooner.)
-
- 31 May, 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 3 commits
-
-
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
-
Jim Fulton authored
setuptools requires that file urls that point to directories must end in a "/". Added a workaround.
-
Jim Fulton authored
install and update methods. - 59270: Buggy recipes can cause failures in later recipes via chdir Also updated a test to reflect logging of script installation.
-
- 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 2 commits
-
-
Jim Fulton authored
-
-
- 06 May, 2007 2 commits
-
-
-
Jim Fulton authored
packages that can't be found or that cause version conflicts. Fixed a renormalizer to prevent spurious test failures,
-
- 20 Mar, 2007 1 commit
-
-
Jim Fulton authored
-
- 19 Mar, 2007 2 commits
-
-
Jim Fulton authored
-
Jim Fulton authored
-
- 18 Mar, 2007 1 commit
-
-
Jim Fulton authored
It wasn't possible to give options on the command line for sections not defined in a configuration file.
-
- 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.
-
- 09 Mar, 2007 2 commits
-
-
Jim Fulton authored
sections.
-
Jim Fulton authored
Treat DistutilsErrors as user errors.
-
- 08 Mar, 2007 1 commit
-
-
Jim Fulton authored
- Added "logical tracebacks" that show functionally what the buildout was doing when an error occurs. Don't show a Python traceback unless the -D option is used. - Added a -D option that causes the buildout to print a traceback and start the pdb post-mortem debugger when an error occurs.
-
- 06 Mar, 2007 2 commits
-
-
Jim Fulton authored
be specified in a versions section. Changed the log format for picked versions.
-
Jim Fulton authored
- The easy_install module install and build functions now accept a versions argument that supplied to mapping from project name to version numbers. This can be used to fix version numbers for required distributions and their depenencies. When a version isn't fixed, using either a versions option or using a fixed version number in a requirement, then a debug log message is emitted indicating the version picked. This is useful for setting versions options. - Added a remove testing helper function that removes files or directories.
-
- 05 Mar, 2007 1 commit
-
-
Jim Fulton authored
no longer causes voluminous setuptools output. Uisng -vv and -vvv now triggers extra setuptools output. Improved a logging message.
-
- 08 Feb, 2007 1 commit
-
-
Jim Fulton authored
-
- 07 Feb, 2007 1 commit
-
-
Jim Fulton authored
```------------ - Added a buildout newest option, to control whether the newest distributions should be sought to meet requirements. This might also provide a hint to recipes that don't deal with distributions. For example, a recipe that manages subversion checkouts might not update a checkout if newest is set to "false". - The recipe-testing support setUp function now adds the name *buildout* to the test namespace with a value that is the path to the buildout script in the sample buildout. This allows tests to use >>> print system(buildout), rather than: >>> print system(join('bin', 'buildout')), Bugs Fixed ``` ------- - Paths returned from update methods replaced lists of installed files rather than augmenting them.
-
- 05 Feb, 2007 1 commit
-
-
Jim Fulton authored
allow for getting less than the newest but still getting what's necessary.
-
- 24 Jan, 2007 1 commit
-
-
Jim Fulton authored
Explicitly specifying a Python executable failed if the output of running Python with the -V option included a 2-digit (rather than a 3-digit) version number.
-
- 22 Jan, 2007 1 commit
-
-
Jim Fulton authored
Feature Changes --------------- - By popular demand, added a -o command-line option that is a short hand for the assignment buildout:offline=true. Bugs Fixed ---------- - When deciding whether recipe develop eggs had changed, buildout incorrectly considered files in .svn and CVS directories.
-
- 17 Jan, 2007 1 commit
-
-
Jim Fulton authored
easy_install APIs. - Added an eggs recipe that *just* installes eggs. - Advertized the scripts recipe for creating scripts. Updated some tests to deal with the fact that setuptools eggs keep oscillating between being files and directories.
-