think at the moment I'm only proposing a change of:

$ pipenv install
Creating a virtualenv for this project...
No package provided, installing all dependencies.
Virtualenv location: /Users/kennethreitz/repos/kr/pip2/test/.venv show the virtualenv location at /Users/kennethreitz/.local/share/virtualenvs etc.

It would have helped me if it said, instead of:

Automatically creates a virtualenv in a standard location.

...perhaps in a central location, but configurable.. But again, it's likely only me that is bugged by the change in policy. I spent quite a while looking for a discussion about the rationale, but couldn't find it. Still, it's a fast-moving project designed to have opinions, and nobody owes me squat. :)