On Fri, Mar 4, 2011 at 6:00 AM, kcrisman <[email protected]> wrote: > > > On Mar 4, 12:17 am, Robert Bradshaw <[email protected]> > wrote: >> On Wed, Mar 2, 2011 at 5:16 PM, kcrisman <[email protected]> wrote: >> >> > On Mar 2, 5:05 pm, achrzesz <[email protected]> wrote: >> >> I'm not sure if this is relevant but >> >> sage: power_mod(2,-1,990) >> >> also gives helpful error message >> >> and checking for exponent -1 is not necessary >> >> A Ch >> >> > Relevant, but of course what I'm really getting at is exactly how to >> > deal with a user who does the original thing (mod(2,990)^-1 ) and is >> > not immediately sure what went wrong because of the lack of error >> > message content. Particularly if it is in the middle of some long >> > script where they forgot to check a gcd condition, for instance. For >> > me personally it is not that big a deal :) >> >> > Any thoughts by those who've worked in integer_mod.pyx? >> >> Wow, that's a pretty bad bug. I'm amazed it's been there so long, I >> guess I've only inverted invertable elements all this time... I'll fix >> it right away. Is there a ticket for it yet? > > I don't think so, because I was hesitant to mess with mpz stuff. > Thanks!
http://trac.sagemath.org/sage_trac/ticket/10873 -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
