Marius Gedminas

Unfortunately removing the wheel doesn't help any: pip 7.x installs source packages by running setup.py bdist_wheel and then installing the resulting whl file. This fails.

There's no reason to remove zc.buildout wheels from PyPI.

IRC: ``` mgedmin: you'd need to modify your setup.py so that bdist_wheel raises an error that'll force pip to fall back to setup.py install ```

FWIW `pip install zc.recipe.egg==2.0.2` also fails with the same error, so it's just a coincidence that this bug showed up right after the universal wheel support got merged.

@wiggin15 what pip version? I wiped my `~/.cache/pip/http` before experimenting, and I checked to see that `~/.cache/pip/wheels/*/*/*/*/` did not have anything named `zc.recipe.egg*`. You can see in [my traceback](https://github.com/pypa/pip/issues/3028#issuecomment-145842506) that...

Ok, as far as I understand: - this problem affects every user of pip 7.x or newer (EDIT: if they have `wheel` installed and don't disable the wheel cache) -...

I would like to see the `pip install -vvv` output of it working in a clean VM without `--no-cache-dir` and with pip 7.x.

Thank you!

Ideas for speeding things up: - add `sudo: false` to .travis.yml (see http://docs.travis-ci.com/user/workers/container-based-infrastructure/) - cache CPython builds (see http://docs.travis-ci.com/user/caching/#Arbitrary-directories)

Bash syntax for this is `${var:-default}` and I would recommend buildout adopt it if this feature is implemented. But do we need this feature at all? What you want can...