On Mar 21, 2:14 pm, Alastair Irving <[email protected]> wrote: > On 21/03/2011 16:24, kcrisman wrote: > > > This is important to fix, because some Sage code depends on the input > > in integer form being Sage integer or something else with Sage > > methods, not a Python int, and one could imagine someone relying on > > this and getting a nasty exception. > > exactly what happened to me, I was relying on having a .n() method to > evaluate numerically. >
Great. This is now http://trac.sagemath.org/sage_trac/ticket/10972. - kcrisman -- 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
