On Sep 9, 7:00 pm, kcrisman <kcris...@gmail.com> wrote: > On Sep 9, 12:40 pm, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > > > On 2010-09-09 14:48, kcrisman wrote:> sage: > > > Exiting Sage (CPU time 0m0.28s, Wall time 0m3.25s). > > > Exiting spawned GP/PARI interpreter process. > > > > Note the last line. This is repeatable. Do we really want this? We > > > do get an exit of a spawned GAP process when one moves Sage to a new > > > location, but that's the only time I can think of that Sage makes such > > > a message without any other programs being started. Don't tell me we > > > started GP/PARI to compute 2+2! Those aren't really the size of > > > integers we should need that for :) > > > The "2+2" has nothing do with it. > > Well, I figured ;) Hopefully it won't be hard to track down.
This may be a side effect of having to send a gp command on startup of the gp interpreter (to turn off the default debugging mode), which may mean that the interpreter is really started up on creation of the interpreter object, every time, instead of only being started when a "real" gp command is needed. That's a non-trivial fix in something I had to work out how to change in the first place; not impossible though. But I will not be able to do this before Saturday... so someone else is welcome to take a look. > > - 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
