3.0.0b1 (2021-03-07)

• Fix issue with combination of> specs andextras and recentsetuptools.

• Fix issue with incrementing options from.buildout/default.cfg.

• Support python37, python38 and python39 in conditional section expressions.

• Fix bootstrapping for python27 and python35.

3.0.0a2 (2020-05-25)

• Ignore.git when computing signature of a recipe develop egg

• Warn when the name passed tozc.recipe.egg:scriptsis not defined in egg entry points.

• Show pip warning about Python version only once.

• Better patch forpkg_resources.Distribution.hashcmp performance.

3.0.0a1 (2020-05-17)

• Scripts: ensure eggs are inserted beforesite-packages insys.path.

• Fix forever loop when changingzc.buildout version viabuildout.

• Add support forRequires-Python metadata.Fragile monkeypatch that relies onpip._internal.Emits a warning when support is disabled due to changes inpip.

• Usepip install instead of deprecatedsetuptools.easy_install.

• Patchpkg_resources.Distribution to make install of unpinned versions quicker.Most obvious withsetuptools.

2.13.3 (2020-02-11)

• Fix DeprecationWarning about MutableMapping.(#484)

2.13.2 (2019-07-03)

• Fixed DeprecationWarning on python 3.7: “‘U’ mode is deprecated”.

2.13.1 (2019-01-29)

• Documentation update for the newbuildout query command.

2.13.0 (2019-01-17)

• Get information about the configuration with new commandbuildout query.

2.12.2 (2018-09-04)

• Upon an error, buildout exits with a non-zero exit code. This now also workswhen running with-D.

• Fixed most ‘Deprecation’ and ‘Resource’ warnings.

2.12.1 (2018-07-02)

• zc.buildout now explicitly requests zc.recipe.egg >=2.0.6 now.

2.12.0 (2018-07-02)

• Add a new buildout optionallow-unknown-extras to enableinstalling requirements that specify extras that do not exist. Thisneeds a corresponding update to zc.recipe.egg. Seeissue 457.

  zc.recipe.egg has been updated to 2.0.6 for this change.

2.11.5 (2018-06-19)

• Fix forissue 295. Onwindows, deletion of temporary egg files is more robust now.

2.11.4 (2018-05-14)

• Fix forissue 451:distributions with a version number that normalizes to a shorter versionnumber (3.3.0 to 3.3, for instance) can be installed now.

2.11.3 (2018-04-13)

• Update to use the new PyPI athttps://pypi.org/.

2.11.2 (2018-03-19)

• Fix for the #442 issue: AttributeError onpkg_resources.SetuptoolsVersion.

2.11.1 (2018-03-01)

• Made upgrade check more robust. When using extensions, the improvementintroduced in 2.11 could prevent buildout from restarting itself when itupgraded setuptools.

2.11.0 (2018-01-21)

• Installed packages are added to the working set immediately. This helps insome corner cases that occur when system packages have versions thatconflict with our specified versions.

2.10.0 (2017-12-04)

• Setuptools 38.2.0 started supporting wheels. Through setuptools, buildoutnow also supports wheels! You need at least version 38.2.3 to get propernamespace support.

  This setuptools change interfered with buildout’s recent support forbuildout.wheel, resulting ina sudden “Wheels are not supported” error message (seeissue 435). Fixed by makingsetuptools the default, though you can still use the buildout.wheel if youwant.

2.9.6 (2017-12-01)

• Fixed: could not install eggs when sdist file name and package name had differentcase.

2.9.5 (2017-09-22)

• Use HTTPS for PyPI’s index. PyPI redirects HTTP to HTTPS by defaultnow so using HTTPS directly avoids the potential for that redirectbeing modified in flight.

2.9.4 (2017-06-20)

• Sort the distributions used to compute__buildout_signature__ toensure reproducibility under Python 3 or under Python 2 when-Ris used onPYTHONHASHSEED is set torandom. Fixesissue 392.

  NOTE: This may cause existing.installed.cfg to beconsidered outdated and lead to parts being reinstalled spuriouslyunder Python 2.

• Add support code for doctests to be able to easily measure codecoverage. Seeissue 397.

2.9.3 (2017-03-30)

• Add more verbosity toannotate results with-v

• Select one or more sections with arguments afterbuildout annotate.

2.9.2 (2017-03-06)

• Fixed: We unnecessarily used a function from newer versions ofsetuptools that caused problems when older setuptools or pkg_resourcesinstalls were present (as in travis.ci).

2.9.1 (2017-03-06)

• Fixed a minor packaging bug that broke the PyPI page.

2.9.0 (2017-03-06)

• Added new syntax to explicitly declare that a part depends on other part.Seehttp://docs.buildout.org/en/latest/topics/implicit-parts.html

• Internal refactoring to work withbuildout.wheel.

• Fixed a bugs inzc.buildout.testing.Buildout. It was loadinguser-default configuration. It didn’t support calling thecreated method on its sections.

• Fixed a bug (windows, py 3.4)When processing metadata on “old-style” distutils scripts, .exe stubsappeared inmetadata_listdir, in turn reading those burped withUnicodeDecodeError. Skipping .exe stubs now.

2.8.0 (2017-02-13)

• Added a hook to enable a soon-to-be-released buildout extension toprovide wheel support.

2.7.1 (2017-01-31)

• Fixed a bug introduced in 2.6.0:zc.buildout and its dependeoncies were reported as picked even whentheir versions were fixed in aversions section. Worse, when theupdate-versions-file option was used, theversions section wasupdated needlessly on every run.

2.7.0 (2017-01-30)

• Added a buildout option,abi-tag-eggs that, when true, causestheABI tagfor the buildout environment to be added to the eggs directory name.

  This is useful when switching Python implementations (e.g. CPythonvs PyPI or debug builds vs regular builds), especially whenenvironment differences aren’t reflected in egg names. It also hasthe side benefit of making eggs directories smaller, because eggsfor different Python versions are in different directories.

2.6.0 (2017-01-29)

• Updated to work with the latest setuptools.

• Added (verified) Python 3.6 support.

2.5.3 (2016-09-05)

• After a dist is fetched and put into its final place, compile itspython files. No longer wait with compiling until all dists are inplace. This is related to the change below about not removing anexisting egg. [maurits]

• Do not remove an existing egg. When installing an egg to a locationthat already exists, keep the current location (directory or file).This can only happen when the location at first did not exist andthis changed during the buildout run. We used to remove theprevious location, but this could cause problems when running twobuildouts at the same time, when they try to install the same newegg. Fixes #307. [maurits]

• Inzc.buildout.testing.system, setTERM=dumb in the environment.This avoids invisible control characters popping up in some terminals,likexterm. Note that this may affect tests by buildout recipes.[maurits]

• Removed Python 2.6 and 3.2 support.[do3cc]

2.5.2 (2016-06-07)

• Fixed-= and+= when extending sections. See #161.[puittenbroek]

2.5.1 (2016-04-06)

• Fix python 2 for downloading external config files with basic auth in theURL. Fixes #257.

2.5.0 (2015-11-16)

• Added more elaborate version and requirement information when there’s aversion conflict. Previously, you could get a report of a version conflictwithout information about which dependency requested the conflicingrequirement.

  Now all this information is logged and displayed in case of an error.[reinout]

• Dropped 3.2 support (at least in the automatic tests) as setuptools willsoon stop supporting it. Added python 3.5 to the automatic tests.[reinout]

2.4.7 (2015-10-29)

• Fix for #279. Distutils script detection previously broke on windows withpython 3 because it errored on.exe files.[reinout]

2.4.6 (2015-10-28)

• Relative paths are now also correctly generated for the current directory(“develop = .”).[youngking]

2.4.5 (2015-10-14)

• More complete fix for #24. Distutils scripts are now also generated fordevelop eggs.[reinout]

2.4.4 (2015-10-02)

• zc.buildout is now also released as a wheel. (Note: buildout itself doesn’tsupport installing wheels yet.)[graingert]

2.4.3 (2015-09-03)

• Added nested directory creation support[guyzmo]

2.4.2 (2015-08-26)

• If a downloaded config file in the “extends-cache” gets corrupted, buildoutnow tells you the filename in the cache. Handy for troubleshooting.[reinout]

2.4.1 (2015-08-08)

• Check theuse-dependency-links option earlier. This can givea small speed increase.[maurits]

• When using python 2, urllib2 is used to work around Python issue 24599, whichaffects downloading from behind a proxy.[stefano-m]

2.4.0 (2015-07-01)

• Buildout no longer breaks on packages that contain a file with a non-asciifilename. Fixes #89 and #148.[reinout]

• Undo breakage on Windows machines wheresys.prefix can also be asite-packages directory: don’t remove it fromsys.path. Seehttps://github.com/buildout/buildout/issues/217 .

• Remove assumption thatpkg_resources is a module (untrue sincerelease ofsetuptools 8.3`). Seehttps://github.com/buildout/buildout/issues/227 .

• Fix for #212. For certain kinds of conflict errors you’d get an UnpackErrorwhen rendering the error message. Instead of a nicely formatted versionconflict message.[reinout]

• Making sure we use the correct easy_install when setuptools is installedglobally. Seehttps://github.com/buildout/buildout/pull/232 andhttps://github.com/buildout/buildout/pull/222 .[lrowe]

• Updated buildout’stravis-ciconfiguration so that tests run much quicker so that buildout is easier andquicker to develop.[reinout]

• Note: zc.recipe.egg has also been updated to 2.0.2 together with thiszc.buildout release. Fixed: Inzc.recipe.egg#custom recipe’srpathsupport, don’t assume path elements are buildout-relative if they start withone of the “special” tokens (e.g.,$ORIGIN). See:https://github.com/buildout/buildout/issues/225.[tseaver]

• download-cache,eggs-directory andextends-cache are nowautomatically created if their parent directory exists. Also they can berelative directories (relative to the location of the buildout config filethat defines them). Also they can now be in the form~/subdir, with theusual convention that the~ char means the home directory of the userrunning buildout.[lelit]

• A new bootstrap.py file is released (version 2015-07-01).

• When bootstrapping, thedevelop-eggs/ directory is first removed. Thisprevents old left-over.egg-link files from breaking buildout’s carefulpackage collection mechanism.[reinout]

• The bootstrap script now accepts--to-dir. Setuptools is installedthere. If already available there, it is reused. This can be used tobootstrap buildout without internet access. Similarly, a localez_setup.py is used when available instead of it being downloaded. Youneed setuptools 14.0 or higher for this functionality.[lrowe]

• The bootstrap script now uses--buildout-version instead of--version to pick a specific buildout version.[reinout]

• The bootstrap script now accepts--version which prints the bootstrapversion. This version is the date the bootstrap.py was last changed. A dateis handier or less confusing than either tracking zc.buildout’s version orhaving a separate bootstrap version number.[reinout]

2.3.1 (2014-12-16)

• Fixed: Buildout merged single-version requirements withversion-range requirements in a way that caused it to think therewasn’t a single-version requirement. IOW, buildout through thatversions were being picked when they weren’t.

• Suppress spurious (and possibly non-spurious) version-parsing warnings.

2.3.0 (2014-12-14)

• Buildout is now compatible with (and requires) setuptools 8.

2.2.5 (2014-11-04)

• Improved fix for #198: when bootstrapping with an extension, buildout wastoo strict on itself, resulting in an inability to upgrade or downgrade itsown version.[reinout]

• Setuptools must be at 3.3 or higher now. If you use the latest bootstrapfromhttp://downloads.buildout.org/2/bootstrap.py you’re all set.[reinout]

• Installingrecipes that themselves have dependencies used to fail with aVersionConflict if such a dependency was installed globally with a lowerversion. Buildout now ignores the version conflict in those cases and simplyinstalls the correct version.[reinout]

2.2.4 (2014-11-01)

• Fix for #198: buildout 2.2.3 caused a version conflict when bootstrapping abuildout with a version pinned to an earlier one. Same version conflictcould occur with system-wide installed packages that were newer than thepinned version.[reinout]

2.2.3 (2014-10-30)

• Fix #197, Python 3 regression[aclark4life]

2.2.2 (2014-10-30)

• Open files forexec() in universal newlines mode. Seehttps://github.com/buildout/buildout/issues/130

• AddBUILDOUT_HOME as an alternate way to control how the user defaultconfiguration is found.

• Close various files when finished writing to them. This avoidsResourceWarnings on Python 3, and better supports doctests under PyPy.

• Introduce improved easy_install Install.install function. This is presentin 1.5.X and 1.7X but was never merged into 2.X somehow.

2.2.1 (2013-09-05)

• distutils scripts: correct order of operations onfrom ... importlines (seehttps://github.com/buildout/buildout/issues/134).

• Add an--allow-site-packges option tobootstrap.py, defaultingto False. If the value is false, strip any “site packages” (as defined bythesite module) fromsys.path before attempting to importsetuptools /pkg_resources.

• Updated the URL used to fetchez_setup.py to the official, non-version-pinned version.

2.2.0 (2013-07-05)

• Handle both addition and subtraction of elements (+= and -=) on the same keyin the same section. Forward-ported from buildout 1.6.

• Suppress the uselessLink to <URL>***BLOCKED*** by--allow-hostserror message being emitted by distribute / setuptools.

• Extend distutils script generation to support module docstrings and__future__ imports.

• Refactored picked versions logic to make it easier to use for plugins.

• Useget_win_launcher API to find Windows launcher (falling back toresource_string forcli.exe).

• Removedata_files fromsetup.py: it was installingREADME.txtin current directory during installation (merged from 1.x branch).

• Switch dependency fromdistribute 0.6.x tosetuptools 0.7.x.

2.1.0 (2013-03-23)

• Meta-recipe support

• Conditional sections

• Buildout now accepts a--version command-line option to printits version.

Fixed: Builout didn’t exit with a non-zero exit status if there was a

failure in combination with an upgrade.

Fixed: We now fail with an informative error when an old bootstrap

script causes buildout 2 to be used with setuptools.

Fixed: An error incorrectly suggested that buildout 2 implemented all

of the functionality of dumppickedversions.

Fixed: Buildout generated bad scripts when no eggs needed to be added

tosys.path.

Fixed: Buildout didn’t honour Unix umask when generating scripts.

https://bugs.launchpad.net/zc.buildout/+bug/180705

Fixed:update-versions-file didn’t work unless

show-picked-versions was also set.https://github.com/buildout/buildout/issues/71

2.0.1 (2013-02-16)

• Fixed: buildout didn’t honor umask settings when creating scripts.

• Fix for distutils scripts installation on Python 3, related to__pycache__ directories.

• Fixed: encoding data in non-entry-point-based scripts was lost.