I don't think it's a Python problem, but rather a Jupyter problem. It used to be the case, and perhaps still is, that we could not distribute ssl because of licensing issues, so when we build our own Python, it may have broken ssl support. This has been true for a long time, so I think that something changed in a recent Jupyter upgrade to require ssl when connecting.
On Thursday, November 5, 2020 at 7:51:43 PM UTC-8, kcrisman wrote: > > > > On Thursday, November 5, 2020 at 10:51:05 PM UTC-5, kcrisman wrote: >> >> >> I have not noticed it before, but *sage-9.2-OSX_10.15.7-x86_64.app.dmg >>> <http://mirrors.mit.edu/sage/osx/intel/sage-9.2-OSX_10.15.7-x86_64.app.dmg> >>> does >>> not work *in macos 10.15.7. !!!!!! >>> >>> I do not understand how a sage for macos 10.15.7 that does not works on >>> macos 10.15.7 has been released. >>>> >>>> >>>> >> Unfortunately I don't think we check many of the binaries. They are >> "just produced"; actually checking they all work can't be automated and can >> be pretty time-consuming (waiting for unpacking etc. >> > > And actually having the right hardware! For the checkers, that is, who > might not be the same as the producers, if that makes sense. > > >> ). Thank you for your report, the SSL problems on Mac have been >> legendary. >> > -- 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 sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/b3cac0e8-8a12-43c9-a494-cb4a85cd028do%40googlegroups.com.
