Steve Dower added the comment: One slight change to the patch for 2.7 - has to catch OSError.
Just realised that I forgot to mention the reason we shouldn't just let the exception propagate out is that we then never load certificates specified by the SSL_CERT_FILE variable. Handling the exception allows a workaround. If the exception occurs and no other certificates have been provided, it seems certain that a later operation is going to fail with a much more useful message (i.e. unverifiable connection, or whatever it says). There are also libraries (I think urllib is the one that was causing me actual trouble) that keep retrying the call when it fails, and all of those would need to be updated to handle this error. The docs don't specify potential exceptions, so I see only good by not raising an exception here. ---------- stage: patch review -> commit review _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27114> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
