pipenv install --deploy --system is not working when using an editable package location #4292
Labels
Type: Bug 🐛
This issue is a bug.
Type: Regression
This issue is a regression of a previous behavior.
Type: Vendored Dependencies
This issue affects vendored dependencies within pipenv.
Milestone
Issue description
After the latest release, the
pipenv install --deploy --system
command started to fail in the CI of a repository I am working on.Expected result
I expected it to succeed without error since we haven't change the Pipfile or our CI setup anytime within the last few weeks and we've run CI multiple times since then. I verified that pinning the pipenv version to the previous version fixed the issue.
Actual result
We get a
TypeError: expected string or bytes-like object
error. For more info please look at:https://travis-ci.org/github/kensho-technologies/graphql-compiler/builds/692595964
Steps to replicate
The Pipfile below is not our original CI Pipfile, but a minimal test case that still displays the issue. I've discovered that the issue appears when we try to install from an "editable package location". (The GraphQL Compiler is the name of the repository I am working on).
This is the Travis CI setup file.
pipenv --support
output:{'implementation_name': 'cpython',
'implementation_version': '3.8.1',
'os_name': 'posix',
'platform_machine': 'x86_64',
'platform_python_implementation': 'CPython',
'platform_release': '5.0.0-1031-gcp',
'platform_system': 'Linux',
'platform_version': '#32-Ubuntu SMP Tue Feb 11 03:55:48 UTC 2020',
'python_full_version': '3.8.1',
'python_version': '3.8',
'sys_platform': 'linux'}
Contents of
Pipfile.lock
('/home/travis/build/kensho-technologies/graphql-compiler/Pipfile.lock'):The text was updated successfully, but these errors were encountered: