--trusted-host not passed to pip when installing from a lockfile #2979
Closed
Description
Issue description
On the latest pipenv release, running pipenv install does not pass --trusted-host to pip.
Running pipenv install xyz does.
Expected result
--trusted-host is passed to pip.
Actual result
> pipenv install --verbose
Installing dependencies from Pipfile…
Installing 'aiohttp'▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 0/7 — 00:00:00
$ ['/Users/tom/.local/share/virtualenvs/tmp.YkTM0kln-68P7VPaZ/bin/pip', 'install', '--verbose', '--upgrade', '--no-deps', '-r', '/var/folders/9w/twrv54nd0v19gsbjhjs3mlhc0000gn/T/pipenv-wgs4narf-requirements/pipenv-h6s3thx1-requirement.txt', '-i', 'http://x.x.co.uk:8080', '--require-hashes']
And:
> pipenv install --verbose pytest
⠋Installing 'pytest'
$ ['/Users/tom/.local/share/virtualenvs/tmp.YkTM0kln-68P7VPaZ/bin/pip', 'install', '--verbose', '--upgrade', 'pytest', '-i', 'http://x.x.co.uk:8080', '--trusted-host', 'x.x.co.uk']
Steps to replicate
Have a Pipfile like this:
[[source]]
url = "http://INTERNAL_PYPI:8080"
verify_ssl = false
name = "xyz"
[packages]
aiohttp = "*"
Notice how the argument is not passed to pip when calling pipenv install.
Metadata
Assignees
Labels
No labels