New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Help] after pypi change pipenv is unsuable when behind proxy. #2011
Comments
Does pip work on its own? |
In order to make pip work, i have to use --trusted-host files.python.org then and then it will work. and somewhere on the issue tracker i read that pipfile's "verify_ssl" will not work (functionality ignored) either. |
Hm this is proxy-related? You can set this as an environment variable, |
yes it a case of corporate network. but thank for your suggestion, PIP_TRUSTED_HOST=files.python.org did work for me, closing now, |
it started happening again for me, even with PIP_TRUSTED_HOST=files.python.org,
|
try |
after change form pypi to new location, pypi.org, pipenv is fairly unusable when connection is behind the firewall(workplace network).
in a pipenv is there any way to disable SSL check false?
I already try to add custom certificate to certifi, and now requests package does work with providing the custom path but not sure how can do the same for pipenv.
The text was updated successfully, but these errors were encountered: