<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello together,</p>
<p>I had the same problem after upgrading to PyQt5 5.13.0 on Python
3.7.3 when I start eric6. The problem is, that Python 3.7.3 and
PyQt5 5.13.0 both have their own libssl-1_1-x64.dll (located in
.\DLL and .\Lib\site-packages\PyQt5\Qt\bin) but in different
versions. Deleting one of them or overwrite one version with the
other make it work, but that's no real solution:</p>
<p>Just upgrade Python to 3.7.4 if possible. There the versions are
mostly identical and Python has renamed it to libssl-1_1.dll so no
DLL-naming collision occurs anymore (maybe with the next update
;-)<br>
</p>
<p>Tobias</p>
<div class="moz-cite-prefix">J. Wester schrieb am 08.09.2019 um
08:02:<br>
</div>
<blockquote type="cite"
cite="mid:CAN2D=csCzLdVw5YsU+s-hmh0iunrWkrBmB+eNdGNv1EJYPQOoQ@mail.gmail.com">
<div dir="ltr">No, I don't, and it isn't for a lack of trying. I
have spent the past few hours trying to reproduce every bit of
relevant code, but I can't seem to get it to recreate in a small
testcase. (The basic snippet exhibiting the bug is literally the
only time anything remotely involving a Qt socket is done in the
program...)<br>
<div><br>
</div>
<div>On a positive note, I had missed one particular line in my
programs debug logs that I had originally missed in the messy
traceback:</div>
<div><br>
</div>
<div>qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS
initialization failed<br>
</div>
<div><br>
</div>
<div>Unfortunately, this doesn't tell us anything new: looking
at the Qt source code it shows that every mention of that
error message is for a failing check against supportsSsl(),
and assuming I read all the defines right, that would likely
be implemented as 'return <span>ensureLibraryLoaded()'...
which the wonderful dialog box already confirmed for me.</span></div>
<div><span><br>
</span></div>
<div><span>Yet tracing it back further, I'd expect to find it in
the implementation of </span><span>q_resolveOpenSslSymbols
in qsslsocket_openssl_symbols.cpp, but I don't see it trying
to access the '</span>OPENSSL_sk_new_reserve' <span>entry
point at all. Hell, I don't see '</span>OPENSSL_sk_new_reserve' <span>mentioned
anywhere in the Qt 5.13 source... so I have absolutely no
clue why it is trying to load that. Then again, making sense
of the #define spaghetti that is supporting all those
OpenSSL versions is way beyond my mere capabilities.</span></div>
<div><span><br>
</span></div>
<div><span>Maybe I'll have some more luck tracking this down
after a good nights rest. Frankly, I am really hoping for it
to be some really stupid mistake on my part at this point.
:-)</span></div>
<div><span><br>
</span></div>
<div><span>Thank you for the assistance thus far. </span></div>
<div>J. Wester</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
PyQt mailing list <a class="moz-txt-link-abbreviated" href="mailto:PyQt@riverbankcomputing.com">PyQt@riverbankcomputing.com</a>
<a class="moz-txt-link-freetext" href="https://www.riverbankcomputing.com/mailman/listinfo/pyqt">https://www.riverbankcomputing.com/mailman/listinfo/pyqt</a>
</pre>
</blockquote>
</body>
</html>