Even though pip is upgraded, some reminescence of old versions still lurks

[nbigaouette]

Missing an example right now, but I think it appears when a pipenv shell is used.

[nbigaouette]

I can't reproduce. Closing.

[nbigaouette]

Seems to be a poetry issue: python-poetry/poetry#732

[nbigaouette]

> cat pyproject.toml
[tool.poetry]
name = "piptest"
version = "0.1.0"
description = ""
authors = ["Nicolas Bigaouette <[email protected]>"]

[tool.poetry.dependencies]
python = "^3.7"

[tool.poetry.dev-dependencies]

[build-system]
requires = ["poetry>=0.12"]
build-backend = "poetry.masonry.api"

> poetry install -vv
Creating virtualenv piptest-py3.7 in /Users/nbigaouette/tmp/piptest/.venv
Using virtualenv: /Users/nbigaouette/tmp/piptest/.venv
Updating dependencies
Resolving dependencies...
   1: fact: piptest is 0.1.0
   1: derived: piptest
   1: selecting piptest (0.1.0)
   1: Version solving took 0.005 seconds.
   1: Tried 1 solutions.

Writing lock file

Nothing to install or update

> poetry run pip -V
pip 19.0.3 from /Users/nbigaouette/tmp/piptest/.venv/lib/python3.7/site-packages/pip (python 3.7)

> ~/.pycors/installed/3.7.3/bin/pip -V
pip 19.1.1 from /Users/nbigaouette/.pycors/installed/3.7.3/lib/python3.7/site-packages/pip (python 3.7)

[nbigaouette]

Could configure's --without-ensurepip flag help this?