#10682: sum fails with lower bound != 0 or 1 (upgrade maxima to 5.26)
-----------------------------------------------------------------------------------------------+
   Reporter:  fmaltey                                                           
               |          Owner:  burcin    
       Type:  defect                                                            
               |         Status:  needs_work
   Priority:  critical                                                          
               |      Milestone:  sage-5.0  
  Component:  symbolics                                                         
               |       Keywords:            
Work_issues:  several doctests need to be patched due to  changes in output 
format/term order  |       Upstream:  N/A       
   Reviewer:                                                                    
               |         Author:            
     Merged:                                                                    
               |   Dependencies:            
-----------------------------------------------------------------------------------------------+

Comment(by jpflori):

 Replying to [comment:40 nbruin]:

 > ideas of dealing with threads either. So, if in `desolve` (conditional
 on domain="real") we just do: ` P("load('contrib_ode)") ... try:
 P("domain: real") soln = P(cmd) finally: P("domain: complex") ` we should
 be fine (the "try ... finally" should guard that we end up with `domain:
 complex`). I don't think performance is a concern if we're doing a "load"
 every time anyway!.^^

 That's the kind of solution I would propose.

 As far as the Maxima instance is concerned, you get it through the
 ._maxima_().parent() call in nintegral(...) and it happens to be the
 unique library instance of Maxima (which is currently used for all the
 calculus stuff). In particular, a call to nintegral should not modify its
 settings.

 To refine Nils answer, Id say that in try we set domain to the option
 passed and in "finally" we should restore the previous value of domain
 which could be "real"rather than "complex" if the user decided to change
 it globally.

 To get the previous value something like str(P('domain').strip(' ') would
 do at the Sage level although this is kind of dirty (and surely slow)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10682#comment:41>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
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-trac?hl=en.

Reply via email to