poetry should upgrade pip and setuptools in virtualenvs it creates

• I am on the latest Poetry version.

• I have searched the issues of this repo and believe that this is not a duplicate.

• OS version and name: RHEL7.5

• Poetry version: Poetry version 1.0.3

Issue

Poetry does not appear to upgrade the version of pip that appears in virtualenvs it creates and manages. This means that, in my case, I get an ancient pip 10.x that doesn’t know to use binary wheels, causing installs of packages to fail as I don’t have python-devel on the machines I deploy to.

When poetry creates a virtualenv, it should, as part of that process, upgrade pip to the latest version available, and continue to upgrade every time it’s about to do anything that installs or removes packages from a virtualenv.

The workaround for me is:

python3.6 `which poetry` shell
pip install -U pip

[kawing-chiu]

I have an idea: maybe pip’s version should be put into pyproject.toml, just like python’s version:

[tool.poetry.dependencies]  
python = "^3.8"
pip = "^19.2"

It can be special-cased so that poetry update will not update it, just like python, unless poetry update pip is called. Initially, poetry can specify a version (range) that it thinks is safe for it.

Here is another example why this is useful: The latest PyQt5 release 5.14.1 switches to the manylinux2014 platform tag, so it’s wheel can only be handled by a very recent pip (only pip versions >= 19.3 recognize this platform tag). If pip’s version can be put into pyproject.toml, it looks like:

[tool.poetry.dependencies]  
python = "^3.8"
pip = "^19.3"
pyqt5 = "^5.14"

Then there is no need for any manual upgrade of pip when the project is installed.

[dbanty]

I think the default behavior is appropriate, pip has been known to make changes that break Poetry, so auto-updating seems dangerous. This is probably more of a feature request for maybe a config setting to auto-update?

As a very slightly easier command you can do poetry run pip install --upgrade pip