-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
SSL Error when installing using private repository with https in pip==20.3 #9182
Comments
How did you install pip? If it is installed from the system package manager (i.e. yum), this should be reported to CentOS instead, since we can’t do anything about packages distributed by Linux distributions. |
This looks like an error that comes from the |
IOW, this error isn't coming from pip, it's coming from the package that's being installed, and pip can't do anything about it. |
I'm installing (or rather upgrading) by running |
Is it a problem with the old version with But regardless, @dstufft is correct, the error is being reported from code related to the (ancient) distribute library. There's no code like that in pip, so this doesn't look like a pip issue. It may be that you have an incompatibility in your requirements (that the old resolver wasn't spotting). The new resolver is stricter and will not install incompatible packages, so it may be wroking back through older and older versions of your dependencies looking for something that works. When it gets back so far that it hits a version that won't even build nowadays (the distribute-related code) it fails. So while we could likely produce a better error message, I suspect that the real issue is that your requirements can't be satisfied in a consistent way, and that's the root cause of your issue here. |
If you could provide the entire output from pip, that'd be ideal. |
Full logs output
|
I'm pretty certain from this that the problem is that pip is backtracking to a point where it's hitting versions so old that they can't be built (because of that distribute hack). We've had a number of discussions about how we "give up" when backtracking is going too far, but we don't (yet) have a good answer on how to decide what constitutes "too far" (there are packages on PyPI that release multiple releases per day, every day, so simple answers like "no more than this many versions" could be problematic). |
I got the same thing. I worked around it by specifying to upgrad pip to 20.2 in my Dockerfile. |
This is now fixed with #9264. |
Environment
Description
Running the command
pip.conf
Getting an SSL error raised trying to install from pypi and my private repository.
Rolling back to pip==20.2.4 fixes the issue for me.
Expected behavior
Setting --trusted-host option should resolve the issue with SSL.
How to Reproduce
Not really sure, but seems like installing from a private repository using HTTPS seems to be the cause.
Output
The text was updated successfully, but these errors were encountered: