Error with `pipenv install --system` with pipenv version `2022.8.19`

Issue description

In our pipeline we install pipenv in a docker container, to test our code. With version 2022.8.15 the command pipenv install --ignore-pipfile --system --dev works as expected. However with version 2022.8.19 it gets lots of errors like:

[pipenv.exceptions.InstallError]: /usr/local/bin/python: can't open file '/usr/local/lib/python3.8/site-packages/pipenv/patched/pip': [Errno 2] No such file or directory

ResourceWarning: Enable tracemalloc to get the object allocation traceback
sys:1: ResourceWarning: unclosed file <_io.FileIO name=14 mode='rb' closefd=True>
ResourceWarning: Enable tracemalloc to get the object allocation traceback
sys:1: ResourceWarning: unclosed file <_io.FileIO name=17 mode='rb' closefd=True>
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/local/lib/python3.8/subprocess.py:946: ResourceWarning: subprocess 283 is still running

An error occurred while installing singledispatch==3.7.0; python_version >= '2.6' --hash=sha256:bc77afa97c8a22596d6d4fc20f1b7bdd2b86edc2a65a4262bdd7cc3cc19aa989 --hash=sha256:c1a4d5c1da310c3fd8fccfb8d4e1cb7df076148fd5d858a819e37fffe44f3092! Will try again.

Expected result

--system flag should work in latest version, as in previous versions, while installing in docker container

Actual result

as seen above

Steps to replicate

• get a docker container / or gitlab pipline
• use python 3.8.12 and run pip install pipenv
• install a Pipfile.lock with pipenv install --ignore-pipfile --system --dev

[FabianClemenz]

@matteius strange behaviour - tried it with pinning the version - works like a charm. I think it will be best, deleting pipenv from our Pipfiles to don’t run in that problem again. Thanks!

[matteius]

@FabianClemenz Well its one of three things … 1.) It could be that the new patch to only include pipenv is more restrictive (intentionally because people needed to be able to pin a specific version of setuptools or pip and before it was adding the entire site directories) https://github.com/pypa/pipenv/compare/v2022.8.15...v2022.8.19#diff-75503dc50a53fd90f7c4e3871006f6c623daa212f5f289c3f4b7aba287c17f9e 2.) It could be because we no longer exclude BAD_PACKAGES which was a temporary fix until the new patch in 1 was figured out, though that seems not it because pipenv wasn’t listed in BAD_PACKAGES https://github.com/pypa/pipenv/compare/v2022.8.15...v2022.8.19#diff-ef852c4ac364f946819f765a6bc26f04f1b0968f31fc512949a60fa2ab0685e8L735 3.) It could be an side effect of using sysconfig instead of distutils (to get 1 to work): https://github.com/pypa/pipenv/compare/v2022.8.15...v2022.8.19#diff-e154923a3c93acd48d40dd714127c4b90cac776ebd71930770919d539d137f77R44

That being said, I am surprised this could have worked on 2022.8.15 because we recently renamed notpip to pip and that was after the version you were installing, plus we changed already to use the vendor’d pip in 2022.8.15 so it should have been trying to do basically the same thing.