Failed to load paths using 2020.6.2

[jiashucheniress]

I can see this issue has previously been raised and resolved before here: #4220, however, I'm still experiencing errors with the latest version of Pipenv which should include the fix.

Issue description

COPY ./docker_image/Pipfile ./docker_image/Pipfile.lock /workdir/
RUN python -m pip install --upgrade pip pipenv \
  && cd /workdir \
  && python -m pipenv install --system --ignore-pipfile --dev

Expected result

Dependencies are installed without error.

Actual result

Installing collected packages: virtualenv-clone, distlib, filelock, appdirs, six, virtualenv, certifi, pipenv
Successfully installed appdirs-1.4.4 certifi-2020.4.5.2 distlib-0.3.0 filelock-3.0.12 pipenv-2020.6.2 six-1.15.0 virtualenv-20.0.21 virtualenv-clone-0.5.4
Installing dependencies from Pipfile.lock (a7add2)…
Failed to load paths: /bin/sh: 1: /root/.local/share/virtualenvs/python_env-rMBEbzCL/bin/python: not found

Output: 
Failed to load paths: /bin/sh: 1: /root/.local/share/virtualenvs/python_env-rMBEbzCL/bin/python: not found

Output: 
Failed to load paths: /bin/sh: 1: /root/.local/share/virtualenvs/python_env-rMBEbzCL/bin/python: not found

[hwmrocker]

I got exactly the same error when I wanted to build a Docker image.
When I tested this with the pipenv version from master, this issue was fixed.

I changed the line to install pipenv from

RUN pip install --upgrade pip pipenv

to

RUN pip install --upgrade pip git+https://github.com/pypa/pipenv

I couldn't find the original issue to comment there, I hope this workaround is useful for someone, until the next version is released.

[jiashucheniress]

found the pull request that seems to have fixed this issue. #4319

Think we can close this one. Looks like we just need to wait for next release.

[jshin49]

This issue is still a problem for me when I installed pipenv using pip. Is it really fixed? Not sure if the PR mentioned by @jiashucheniress addresses this issue.

[jiashucheniress]

This issue is still a problem for me when I installed pipenv using pip. Is it really fixed? Not sure if the PR mentioned by @jiashucheniress addresses this issue.

hi @jshin49 , the issue is fixed on master, however, the fix hasn't been released yet. atm the way I'm by passing it is by doing the following

python -m pip install git+https://github.com/pypa/pipenv@97324a6932b3fda0ccbabcc349474d74a913e0bc

This takes the master commit with the fix, but not all of the subsequent changes