I don't see any connection between:

* SSL cert failures when using  python provided by "macOS/XCode" 
* The existence of Sage's python spkg

I have been seeing those cert failures for years now.  I have never had any 
trouble with Sage's python spkg.  It has always built cleanly for me.  So 
this not only sounds like a broken record, it has nothing to do with the 
issue at hand.

There have been many times when I have had to download a Sage file with my 
browser and move it into the "updtream" directory due to SSL cert 
failures.  And that has literally been true for years.

- Marc

On Saturday, February 22, 2025 at 7:26:12 AM UTC-6 [email protected] wrote:

> Dear all,
>
> To summarise what I found qua Mike's installation issues:
>
> It seems that macOS/XCode stopped providing Pythons what are good enough 
> to use to
> install Sage from source, as their networking is broken in some way
> which make it impossible to fetch packages for 
> installation. The main symptome looks like an SSL cert check failure
> while fetching pip spkg tarball by sage_bootstrap/download/transfer.py:
>
> [pip-24.2] Attempting to download package pip-24.2-py3-none-any.whl from 
> mirrors
> [pip-24.2] 
> https://github.com/sagemath/sage/releases/download/10.6/pip-24.2-py3-none-any.whl
> [pip-24.2] 
> [xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx]
> [pip-24.2] ERROR [transfer|run:135]: [Errno socket error] [SSL: 
> CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local 
> issuer certificate (_ssl.c:992)
>
> [....]
>
> [pip-24.2] File 
> "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/ssl.py", 
> line 1346, in do_handshake
> [pip-24.2] self._sslobj.do_handshake()
> [pip-24.2] ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] 
> certificate verify failed: unable to get local issuer certificate 
> (_ssl.c:992)
> [pip-24.2]
> [pip-24.2] The above exception was the direct cause of the following 
> exception:
> [pip-24.2]
> [pip-24.2] Traceback (most recent call last):
> [pip-24.2] File "/Users/mike/sage/build/bin/../sage_bootstrap/tarball.py", 
> line 185, in download
> [pip-24.2] Download(url, destination).run()
> [pip-24.2] File 
> "/Users/mike/sage/build/bin/../sage_bootstrap/download/transfer.py", line 
> 137, in run
> [pip-24.2] raise error
> [pip-24.2] File 
> "/Users/mike/sage/build/bin/../sage_bootstrap/download/transfer.py", line 
> 128, in run
> [pip-24.2] filename, info = opener.retrieve(
> [pip-24.2] ^^^^^^^^^^^^^^^^
> [pip-24.2] File 
> "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/urllib/request.py",
>  
> line 1821, in retrieve
> [pip-24.2] fp = self.open(url, data)
> [pip-24.2] ^^^^^^^^^^^^^^^^^^^^
> [pip-24.2] File 
> "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/urllib/request.py",
>  
> line 1793, in open
> [pip-24.2] raise OSError('socket error', msg) from msg
> [pip-24.2] OSError: [Errno socket error] [SSL: CERTIFICATE_VERIFY_FAILED] 
> certificate verify failed: unable to get local issuer certificate 
> (_ssl.c:992)
>
> These capabilities are not tested by ./configure
>
> The Python I'm talking about is not to be confused with tests to use 
> "system" Python to run sagelib,
> these tests are more detailed, in particular availability of Python modules
>
> sqlite3, ctypes, math, hashlib, socket, zlib, ssl, ensurepip
>
> is checked. I don't know whether a modern (Troyan horse) Python from Apple
> lacks some of these modules, or perhaps some of these modules are
> broken.
>
>
> ----------------------------------------------------------------------------------
>
> To me, the right course of action is to purge from Sage its
> (half-broken anyway) capabilities to build Python (as on macOS there is an 
> abundance of Pythons either
> from python.org or from Homebrew, and building Python is tricky do to
> due to SSL issues); then all this mess would not have arisen in the 1st 
> place.
>
> And, sorry for sounding like a broken record: building and providing 
> Python should be
> left to experts, are we are not experts in this.
>
> Dima
>
>
> On Fri, Feb 21, 2025 at 12:11:48AM -0800, Mike Wirth wrote:
> > <David Roe suggested that I post this here, as well as having done so on
> > zulipchat>
> > 
> > Sage newbie. here, but long term Mac, etc., user and developer. Did 
> serious
> > early work with algebraic manipulation system, Macsyma, including doing
> > internal mods in Lisp for 2D display of math expressions (pre-Latex).
> > Especially interested in the manifolds package for tensor calculus.
> > 
> > My primary Sage installation is on an old MacBook Pro (2014-vintage, 11,3
> > model) but running current macOS 15..3.1, patched with OCLP 2.2.0, built
> > from downloaded binaries. Since I expect to want to inspect and possibly
> > modify Sage internals, I tried building from source on this machine. Very
> > frustrating. Despite Dima's excellent repeated help, wasn't able to
> > successfully complete the build. Encountered a circular set of errors,
> > dealing with Python and pip versions, certificates, etc., Put the effort 
> on
> > the back burner pending a better understanding of the issues.
> > 
> > However, using this MacBook Pro with the Parallels Desktop system and a
> > Ubuntu 22.4 VM, I did complete a from-source build. And installed Ubuntu
> > 24.1 LTS directly on another MacBook Pro (9,3) and a Sage from-source 
> build
> > there. So now I'm set to explore Sage for my purposes.
> > 
> > But I still want to be able to do a clean build from source on current
> > macOS versions. Are there developers in this community with similar
> > interests? I would be interested in collaborating with you on making the
> > build process on macOS more robust. Feel free to respond to this post or
> > directly to me to see if there's a practical path forward.
> > 
> > Mike
> > Silicon Valley
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "sage-devel" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to [email protected].
> > To view this discussion visit 
> https://groups.google.com/d/msgid/sage-devel/CAFpc19Xw1Nbn87AooOpRp9vwD168UpcZOCMUykLv0O9FLUbYhA%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/sage-devel/8301c6f3-39f0-4a49-afe6-8b12e2c4be5dn%40googlegroups.com.

Reply via email to