if it's PARI-dependent, it makes sense to upgrade PARI to the latest version. PARI used by Sage is almost 2-year old. They rolled out two upgrades in the meantime.
Dima On Mar 6, 6:41 am, mhampton <hampto...@gmail.com> wrote: > I tried to confirm that fix, and realized that this problem isn't > occuring on my mac (running 10.6.2). Strange. > > -Marshall > > On Mar 5, 3:25 pm, Gonzalo Tornaria <torna...@math.utexas.edu> wrote: > > > > > On Fri, Mar 5, 2010 at 10:47 AM, Simon King <simon.k...@nuigalway.ie> wrote > > > > Hi! > > > > I created a ticket at > > > http://trac.sagemath.org/sage_trac/ticket/8444 > > > I think this is caused by a duplicate _sig_on in the bottom part of > > pari.__call__. > > > I'll post details and (possible) solution later (feel free to ping me > > in a few days if I forget). > > > Best, > > Gonzalo -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
