Oh, right, this certainly has nothing to do with sagenb, what is not stopped is sage worker that does the computation itself, right?
Could it be that you updated your OS in the meantime, and if you roll back to sage 7.3 you would still see the same behaviour? On sage's side it might be ipython update, although I am guessing. There is a debugging technique that would let you find a git commit that caused the change you noticed, using git bisect, although this might take a full day of work or so, just because there were few hundred commits and you would need to run 'make build' a dozen times or so, with testing after each rebuild... -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
