This significantly improves performance, since it allows the remote
server to directly stream a tarball that just contains the requested
revision rather than the full repository contents.
Add a new testsuite option `--use-venv` to enable the use of `venv`
for creating a test virtual environment. The option is opt-in because
creating a `venv` environment does not work right when running under a
`virtualenv`; which is why `tox-venv` must be used in combination with
tox.
Speeds up the end-to-end running time for Travis tests.
* Adds a new jobs to test_install* separately (using -k "[not] test_install")
* More generic cache ignore
* Move slower Python 3.5 tests before 3.4
* Factor tox envs
Since de-vendoring support exists only for downstream, and they need
to patch pip to get that support anyways, it seems reasonable to push
support for testing that configuration onto them. This is something
they need to do anyways, since they need to test their versions of the
vendored libraries.
See https://github.com/pypa/pip/pull/4657 for more information.
* Upgrade to Trusty on Travis
Before Travis pushes us forcefully, it makes sense to ensure that the flip won't break our builds.
* Show failures because travis misbehaves occasionally
* Try out newer PyPy versions on Travis
* Use pypy and pypy3
🎉
* Revert "Show failures because travis misbehaves occasionally"
This reverts commit 7434fd6103.
* Allow PyPy3 to fail
* Try using a different version of pypy
* Try everything
* Switch to simpler names
* Try using container build with newest PyPy
* Use container build everywhere
* Remove a useless job
The wheel based vendor tests should get us the same testing without
the issue of trying to upgrade something that setuptools itself is
depending on. It also matches the mechanism that downstream are
currently using better.
