Invoking _get_runnable_pip
to install setuptools is problematic
#11389
Labels
type: bug
A confirmed bug or unintended behavior
Description
This may or may not be a pip bug, but I am stumped trying to figure it out and does involve pip so I am hoping for some help. In pipenv we used to invoke
pip
but recently changed to invoke_get_runnable_pip
to ensure we use our vendor'd version of pip which is currently the latest22.2.2
. The problem is that get this released, I excluded a list ofBAD_PACKAGES
from the install phase which includessetuptools
because I figured its already provided by the virtualenv, but some users wish to install a specific version ofsetuptools
different from this --which is where the problem exists.pipenv
itself hassetuptools
in its lock file as well, and when I remove theBAD_PACKAGES
work-around for this issue, I find that the pip runnable removes setuptools and then the new setuptools fails to install becausepkg_resources
is no longer available, presumable because the prior version ofsetuptools
had just been removed. I am having trouble figuring out how to get this working the way it was working when justpip
was invoked and this scenario worked.This issue occurs during the dependency setup before the test runner ever has a chance to run, but I am not sure why its happening like this and would love any help trying to understand what the difference is.
Expected behavior
the
_get_runnable_pip
should be able to upgrade setuptools the waypip
does when its invoked.pip version
22.2.2
Python version
3.7,3.8,3.9 (weirdly python 3.10 works)
OS
linux/windows/mac
How to Reproduce
Haven't been able to reproduce this locallyI was just able to reproduce it by creating my pipenv virtualenv with python3.8 - it works fine on python 3.10. github actions for pipenv cannot get to running the tests due to this issue trying to upgrade setuptools using_get_runnable_pip
as well on anything other than python 3.10Output
For more details on the dependency installation failure runs: https://github.com/pypa/pipenv/runs/7909760557?check_suite_focus=true
Code of Conduct
The text was updated successfully, but these errors were encountered: