Jori, sorry for crying out loud, but noone is going to work on sagenb, besides maybe you, I think. Messing around with 11 years old web technology is very hard indeed.
What exactly are you missing from jupyter nb, or jupyter hub, or some version of SMC people managed to get running on their intranets? Dima PS. Reverting to an older sagenb should work, via reverting the corresponding commits, etc... On Thursday, September 7, 2017 at 6:24:07 AM UTC+1, Jori Mäntysalo wrote: > > On Wed, 6 Sep 2017, kcrisman wrote: > > > I suspect perhaps > https://github.com/sagemath/sagenb/commit/9dd5c0f8c783de7cb0ae21c9f445ab8260b5a0ac > > is the culprit, and > > put something on #432 to the author of that change. It seems like the > kind of thing that might happen when a module is > > updated, as that change did, though I could be barking up the wrong tree > too. Thanks for pursuing this. > > Another question: Can I downgrade SageNB when waiting correction for this > bug? Is so, how? > > -- > Jori Mäntysalo -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
