On Friday, November 6, 2020 at 9:32:51 AM UTC-8, John H Palmieri wrote: > > I don't think it's a Python problem, but rather a Jupyter problem. It used > to be the case, and perhaps still is, >
Yes, still is - we are waiting for the OpenSSL 3.0 release, which will solve this issue - see https://trac.sagemath.org/ticket/29555 > 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. > That's right, it was the tornado upgrade - see https://trac.sagemath.org/ticket/30556 -- 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/ffefc692-009a-4ef2-ab1b-a80a3e76ae51o%40googlegroups.com.
