Easier way to keep pip up to date

[uranusjr]

Not sure if this is a good idea, but throwing it out here first.

pip 9.0.3 recently came out and I started to get the upgrade message everywhere, but the message can be a little misleading for PIpenv users

You are using pip version 9.0.2, however version 9.0.3 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.

This is not the command to run unless you’re in the subshell (you need the pipenv run prefix), and may cause confusion. Neither pip nor PIpenv is doing things wrong here, but I feel the UX can be improved.

Some wild thoughts—

• Use --disable-pip-version-check when invoking pip as a subprocess to avoid the message from appearing, and/or hijack it to display our own version.
• Make pipenv sync or pipenv install take care of upgrading pip in the virtualenv.

[techalchemy]

We can just use the temp_environ() context manager when we run pip and set PIP_DISABLE_PIP_VERSION_CHECK which I assume works like any other pip environment variable?

[uranusjr]

Yes, probably. The thing is if we turn off the pip upgrade notice, Pipenv will need to offer its own way to keep pip up-to-date.

[matteius]

pipenv relies on its vendor'd pip now - it no longer calls it out as an install time requirement, though virtualenv installs pip anyway into the virtualenv which seems fine as users can invoke pip to install/remove a package with intend to bypass Pipfile/Pipfile.lock. I am not sure that there is a TODO here anymore.