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
