-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
setup downloads sometimes fails CERTIFICATE_VERIFY_FAILED #14169
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
Comments
This should probably be gated on |
Agreed, so I am not aware of what this actually means for you... Hence I suspected it could be something like: try:
old-method
except Exception as e:
if "CERTIFICIATE_VERIFY_FAILED" in str(e):
import certifi ... but I am not sure what is the best way. |
I was thinking try:
import certifi
ca_path = certifi.where()
except ImporError:
ca_path = None to avoid having the two copies of the |
Yeah, that is a good idea! But I don't know if |
Re-milestoned this to oldest version of Matplotlib this is going to be supported in the near future. |
This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help! |
|
Bug report
Sometimes (depending on how Python has been installed) one might see a
error.
Fix
The easy fix is to ensure
certifi
certificates path is added to theurlopen
method.I.e. in your
setupext.py
you may need:Probably there needs to be some try-execpt-(import certifi-fix) to handle this.
Matplotlib version
This happens when
setup.py
tries to download files, e.g. the recent change to jquery download. So basically I have only seen this in 2.2.4 and 3.0.3.Agreed, this may be because my installation is not the same as system installations, but it may happen elsewhere I guess.
The text was updated successfully, but these errors were encountered: