It turns out that the bug underlying this has already been fixed in
ticket 5434 which has been merged in 3.4.rc1, so this problem will not
arise once 3.4 has been released.
2009/3/7 John Cremona :
> It is now ticket number 5451: see
> http://trac.sagemath.org/sage_trac/ticket/5451
>
> John Cremo
It is now ticket number 5451: see http://trac.sagemath.org/sage_trac/ticket/5451
John Cremona
2009/3/7 John Cremona :
> I am hoping that someone who has worked on that code, such as Martin
> Albrecht, might reply as might know what is going on. It should not
> be too hard to fix.
>
> I could no
I am hoping that someone who has worked on that code, such as Martin
Albrecht, might reply as might know what is going on. It should not
be too hard to fix.
I could not find a relevant trac ticket so am opening one now.
John Cremona
2009/3/7 Alex Lara :
>
> Just as I thought. So there is nothi
Just as I thought. So there is nothing I can do but work with sage
3.1.1, right?
Those polynomials arised as coefficients of some polynomials in F_q(t)
[T] and inside a sum command:
sum ( (do something with H_j(T)) for j in bla bla)
The routine which gave the error was successfully used many ti
That is definitely a bug. Doing it step by step works:
sage: fd=f.denominator(); gd=g.denominator()
sage: fn=f.numerator(); gn=g.numerator()
sage: fn*gd+fd*gn
2*t^18 + t^11 + t^10 + 2*t^2
sage: hn = fn*gd+fd*gn
sage: hd = fd*gd
sage: hn.gcd(hd)
t^3 + 2*t^2
sage: hn/hd
(2*t^15 + 2*t^14 + 2*t^13 +
