> Are the bugs over all fields, e.g.? Maybe thats a way to narrow it down?
Another way to narrow down issues in 'factory' would be to upgrade to recent Singular. There of course still bugs in, but I did not catch them yet, or reported bugs were not tracked down to 'factory' ;-) I'm working on the upgrade to 4.0.1 ( #17254 <http://trac.sagemath.org/ticket/17254>) Maybe I will finish in a couple of days, maybe it will need one or two weeks. The various issues in polynomial rings over Integers (ZZ) are not fixed yet. Adi Popescu is working on that. Typical bugs in 'groebner()' are premature termination http://www.singular.uni-kl.de:8002/trac/ticket/629 non-reduced tail, eating all memory (same examples finish in Macaulay2 in a bit) or running forever. Am Freitag, 13. Februar 2015 12:22:24 UTC+1 schrieb Volker Braun: > > Are the bugs over all fields, e.g.? Maybe thats a way to narrow it down? > > Were you going to set the tickets to needs review after working more on it? > > Maybe we should add a boolean flag factorize(proof=None) and optionally > check the result depending on the base ring, isn't that much cheaper than > computing the factorization anyways? > > > On Friday, February 13, 2015 at 12:02:06 PM UTC+1, Jakob Kroeker wrote: >> >> Factory is notoriusly buggy; it improved over time, but it is still >> buggy. There are more than 20 bugs in factory which are fixed in 4.0.1 but >> not in 3.1.7 >> So, if I understand it right, stopgap is to warn the user if it is known >> that there are bugs leading to wrong results. >> > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
