Many thanks for your reply and warning! I would nevertheless like to try and see if I can get this sage package on my machine---if only just to see the bug in action myself. Do you know what might be causing the error I'm getting with "sage -i"?
Regards, Jeremy On Monday, July 13, 2015 at 2:12:35 PM UTC-4, Nathann Cohen wrote: > > Hello! > > >> (with the bug fixed?). >> > > No, the bug has not been fixed despite having been reported regularly > (with reminders) to the authors. If you like this feature, please consider > writing to the authors to tell them so, and ask them to solve this problem: > https://groups.google.com/d/msg/sage-support/Iha5__c_h44/ZGRgZQRnsnkJ > > I think of this code from time to time, and I was about to create a ticket > to remove it from Sage two weeks ago. The feature is nice, but the code > returns wrong results and is apparently unmaintained. We cannot host it > forever in this state. > > Nathann > -- 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 http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
