> In fact, any code that blatantly gives mathematically incorrect results > should -- in my opinion -- always be marked a BLOCKER in > trac. No matter whether the relevant mathematics is small or > big or important or not. If nothing else, if a function is known > to return false results on any input, we should do something > to make that crystal clear (in the docs, print warnings, etc.), even > if we can't easily fix the problem.
In any case, it's now in. Michael Abshoff added the G2 fix this morning. Dan --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
