A working_set passed into install() is the sign that we're called from
buildout.py to install buildout, setuptools, an extension or a recipe.
Those need the global pkg_resources.working_set, for instance to load entry
points.

So... conflicts with global packages are possible, but they should be ignored
so that we can grab the right versions ourselves. The paths that end up in the
bin scripts that we generate are OK.

Fix for buildout 2.2.3 upgrade/downgrade problems

non-matching versions.

Ignoring version conflicts for buildout and setuptools, this enables
buildout/setuptools upgrades/downgrades after a bootstrap.

Whatever the method we used to find it, cache the result. Not just in one of
the cases. And it makes the method more readable as it doesn't mix functionality

Often it is unclear why buildout takes a long time on something, this logger
statement might make it much clearer

This way it is more clear that we're trying several things one after the
other. And it is nicer to read this way.

- Performance enhancment via https://github.com/buildout/buildout/pull/194
- Fix manifest

193 performance

Introduce improved easy_install.py Install.install function. Originally commited in 98b7c55c

Fix for #184

See #184, a comma doesn't work (like it *does* inside a logger call) inside an exception.

Close various files when finished writing to them; fixes ResourceWarnings and some PyPy uses.

Unify three checks for a file being changed into one function. Note that python < 3.3 raise IOError if a file is not found, while python >= 3.3 raise FileNotFound, a kind of OSError. EnvironmentError is a common superclass on all versions and in fact is where `errno` is defined.

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

Fix Python tarball download in Makefile by following HTTP redirects

List Python 2 and 3 support in setup.py

Open files for 'exec()' w/ universal newlines.

Fixes #130.

The SSL patch file was recently renamed[1], and then fixed to apply
against 2.6.9rc1[2].

[1] https://github.com/collective/buildout.python/commit/ad45adb78bfa37542d62a394392d5146fce5af34
[2] https://github.com/collective/buildout.python/commit/8d58e4b2bc67ef67d97013a66e8aa4669b3a37a1

Since buildout is still building Python 2.6.8 we should use a URL to a
version of the patch that applies to 2.6.8.

I noticed this problem while idly browsing Travis CI:
https://travis-ci.org/buildout/buildout/jobs/12570074