pip does not connect: no ssl
I'm trying to install a package with pip, and I get this message. A quick web search suggests that pip may be out of date or in need of a recompile.
TIA John. WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available. WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.",)': /simple/protobuf/ WA |
You might want to mention what version of Slackware you are running and if you have applied all of the updates.
That will help us help you, after all. |
And this should be an issue with your installation or configuration unless your Slackware be very old as this module is shipped in the python packages since Slackware 13.0
|
Yeah. I shudda told you what I was running. It's slackware64-current, and I am up-to-date with the latest good stuff with slackpkg-plus.
Anyway, my pip is toast for SSL stuff right now, which is not good. John. |
Please post the out put of:
Code:
find /usr/lib64 -name ssl.py |
That find statement shows this.
/usr/lib64/python3.7/ssl.py /usr/lib64/python2.7/ssl.py I added the 3.7 a few days ago for something else; /usr/bin/python points to the 2.7 version. John. |
How did you install pip? Do you use a virtual environment? If yes how is it set up?
|
How did I install pip? I did not, but slackware did.
So does it work for you? When I run pip list, I get this: WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available. Could not fetch URL https://pypi.org/simple/pip/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/pip/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.",)) - skipping |
Which Slackware version are you running? pip is not shipped in Slackware version 14.2
|
Please read #4 above. (Hint: It's slackware64-current)
BTW: I can forget about this issue because I solved it another way. What I was doing was trying to build mysql-workbench for my slack installation. I've got all of the deps built now, but the mysql-workbench build is stopping with an error around 90 percent. I've got a bug report into mysql, but if anyone knows a handy way to get a gui for the mysql installation, it would be welcomed. John. |
Quote:
Quote:
So my current assumption is that somehow you managed to create the issue you mention. Without more information about your configuration I can't help you, sorry |
That's true, but it does not affect pip that runs with python-2.7.
How is there a problem? My big issue is the gui for the database. John. |
Make sure you have curl installed.
|
HQuest sent me on the right path, and I'm now fixed. I'll explain how.
I spent the last few days futzing with curl and openssl. The problem was that I used slackpkg+ to keep current. What I did not know until a few minutes ago was that the multilib versions did not do a full install. I just slackpkg reinstall curl and slackpkg reinstall openssl. It works again, and goodies like darktable build again :-) I'll get back to mysql-workbench in a few days. I really want to do some sql stuff for fun and entertainment. Thanks again HQuest. John. |
All times are GMT -5. The time now is 11:31 PM. |