John Nagle wrote:
> John Nagle wrote:
>> I just "upgraded" from M2Crypto 0.17 to M2Crypto 0.18, and I'm
>> running my regression tests. I'm seeing occasional cases where
>> M2Crypto raises the exception SSL.SSLError, and the associated
>> error is "(0, 'Error')", which is the bogus error you get if you feed
>> 0 to
>> "perror". It failed once on "verisign.com"'s cert, then worked
>> on the next try.
>>
>> This is on Windows, running Python 2.4 (which is what M2Crypto
>> supports on Windows.)
>>
>> I'm trying to make this reproduceable. More later.
>>
>> John Nagle
>
> Still trying to reproduce this. Every time except the first,
> the regression test passed. More later. Might be an uninitialized
> variable in a DLL, or something like that.
>
> John Nagle
Still having trouble reproducing the problem. But somewhere,
something raised that bogus no-error exception three times.
Anything that returns "(0, 'Error')" as exception data is a bug.
John Nagle
--
http://mail.python.org/mailman/listinfo/python-list
