-
Notifications
You must be signed in to change notification settings - Fork 41
Description
This is going to be a highly system dependent issue, so please bear with me....
Is there a specific reason for including the pip-system-certs dependency in this project?
I've traced an issue creating my virtual environment to this dependency in some of my environments where the system certificate store could very well be insufficient to rely on. I do have a custom pypi source defined in my Pipfile whose certificate was issued by Let's Encrypt. My project is using pipenv, and if I do a dirty hack and remove the pip-system-certs entry from Pipfile.lock, everything appears to work.
I know this will highly depend on the system you run it on, but in my opinion that is part of the problem.
Here is a minimal Pipfile example where I could reproduce the issue
[[source]]
# internal pypi server whose cert was issued by Let's Encrypt
url = "https://pypi.example.com/simple/"
verify_ssl = true
name = "internal-pypi"
[packages]
inventree = "*"
[dev-packages]
black = "*"
bump2version = "*"
flake8 = "*"And I could reproduce with
pipenv lock --devpipenv sync --dev- Observe failure
- Preform dirty hack and remove the
pip-system-certsentry fromPipfile.lock pipenv sync --dev- Observer successful environment creation