Ask Your Question
0

Pip ssl errors

asked 2020-11-21 22:03:13 +0100

watson_ladd gravatar image

updated 2020-11-22 08:25:37 +0100

FrédéricC gravatar image

Fresh install on Mac OS X 10.14.6

$sage -pip install pycryptodome

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/pycryptodome/ ERROR: Could not find a version that satisfies the requirement pycryptodome (from versions: none) ERROR: No matching distribution found for pycryptodome 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

edit retag flag offensive close merge delete

Comments

Worst this happens when installing the SSL module also.

watson_ladd gravatar imagewatson_ladd ( 2020-11-21 22:46:49 +0100 )edit

We have endured thisssl pain in our collective ass since the origin of times, and this will subside until OpenSSL receives a GPL-compatible license. Since it is not yet the case, we cannot distribute OpenSSL with Sage source or in precompiled packages (some precompiled packages depending on, but not containing, OpenSSL are available for various Linux distributions).

When compiling Sage by yourself, it is enough to install OpenSSL (and its development packages). I amnot aware of the solution to use to enable it in precompiled packages/distribution ; furthermore, I am aware that Apple's shenanigans with Xcode complicate the problem even further.

Could you forward your question to sage-support ?

Emmanuel Charpentier gravatar imageEmmanuel Charpentier ( 2020-11-21 23:06:01 +0100 )edit

Is there no way to make pip work with NSS instead?

watson_ladd gravatar imagewatson_ladd ( 2020-11-22 19:38:41 +0100 )edit

1 Answer

Sort by » oldest newest most voted
2

answered 2020-11-22 03:41:35 +0100

slelievre gravatar image

updated 2020-11-22 03:48:40 +0100

If installing from binaries, once installed, fix using

If compiling from source, try installing as many things as possible from Homebrew.

In particular, OpenSSL, and ideally Python too (currently Python 3.8 works best).

$ brew install openssl python@3.8
$ cd <path_to_sage_directory>
$ git pull origin master --tags -q  # replace master by develop if adventurous
$ source .homebrew-build-env
$ make configure
$ ./configure
$ make -s V=0

Or try installing with Conda. See:

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2020-11-21 22:03:13 +0100

Seen: 1,037 times

Last updated: Nov 22 '20