On Jul 14, 2014, at 10:20 PM, Dimitri John Ledkov wrote:
>> try:
>> + from httplib2 import SSLHandshakeError
>> +except ImportError:
>> + from httplib2 import HttpLib2Error as SSLHandshakeError
>> +try:
>
>yes, it does. But it's only used to catch the error, and re-raise it with a
>helpful message that "there is an option to ignore ssl certificate
>errors". The actual class of the error has changed, but i believe the text of
>the error comes from the underlying library. This keeps compat in python2,
>and the worst case scenario the error is re-raised regardless.
So I had a look at the actual code where this is used. Ug.
>Maybe I should remove all error catching and thus not use either
>SSLHandshakeError nor HttpLib2Error?
That does seem better. Then release notes or documentation can describe
LP_DISABLE_SSL_CERTIFICATE_VALIDATION.
On Jul 14, 2014, at 10:20 PM, Dimitri John Ledkov wrote:
>> try:
>> + from httplib2 import SSLHandshakeError
>> +except ImportError:
>> + from httplib2 import HttpLib2Error as SSLHandshakeError
>> +try:
>
>yes, it does. But it's only used to catch the error, and re-raise it with a
>helpful message that "there is an option to ignore ssl certificate
>errors". The actual class of the error has changed, but i believe the text of
>the error comes from the underlying library. This keeps compat in python2,
>and the worst case scenario the error is re-raised regardless.
So I had a look at the actual code where this is used. Ug.
>Maybe I should remove all error catching and thus not use either
>SSLHandshakeError nor HttpLib2Error?
That does seem better. Then release notes or documentation can describe SSL_CERTIFICATE _VALIDATION.
LP_DISABLE_