On Jun 30, 3:07 am, Robert Bradshaw <rober...@math.washington.edu> wrote: > On Jun 29, 2010, at 12:45 PM, kcrisman wrote: > > > Dear all, > > > Does anyone know what is going on here (the double Maxima exit)? It > > must have something to do with the sum loading, I guess, since this > > doesn't happen with integration (see below). If someone has an older > > Sage it would be worth testing to make sure this happens there (this > > was all incorporated in Sage 4.2.1, I think, and I don't think has > > changed much since then). Doing the steps in the code 'by hand' does > > not yield the double exit. Thanks! > > The calculus module uses its own instance of maxima so that it won't > mess up any user's maxima session (and visa-versa). This is almost > certainly where the double exit is coming from.
Yes, I know. But I can't figure out where a different Maxima is used - symbolic_sum lives in calculus.py, so it should be using the calculus Maxima, right? I just can't figure out where two different Maximas (Maximae?) are being used here, and I'd appreciate help tracking it down :( - kcrisman -- 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
