#13364: Upgrade Maxima to 5.29.1
------------------------------------------------------------------+---------
       Reporter:  kcrisman                                        |         
Owner:  tbd                                                 
           Type:  enhancement                                     |        
Status:  needs_work                                          
       Priority:  major                                           |     
Milestone:  sage-5.6                                            
      Component:  packages                                        |    
Resolution:                                                      
       Keywords:  maxima spkg                                     |   Work 
issues:  fix doctests                                        
Report Upstream:  Reported upstream. Developers acknowledge bug.  |     
Reviewers:  Karl-Dieter Crisman, François Bissey, Leif Leonhardy
        Authors:  Jean-Pierre Flori                               |     Merged 
in:                                                      
   Dependencies:  #13860                                          |      
Stopgaps:                                                      
------------------------------------------------------------------+---------

Comment (by dimpase):

 I'm doing {{{git bisect}}} on the Maxima repo to try to find the places to
 blame. It looks it was a long story, more than just a single change to
 undo. The first bad commit after the clean situation, as if in 5.26.0, is
 {{{
 4e2e7fb738e6f9f1955a5378ae392a1930b30bce
 Merge branch 'share-cleanup-branch-2011-10'
 }}}
 Maxima identifies itself as {{{Maxima 5.26.0_70_g4e2e7fb_dirty}}}, and one
 gets
 {{{
 sage: var('a');assume(a>0);limit(x^a,x=0)
 a
 ERROR: An unexpected error occurred while tokenizing input
 The following traceback may be corrupted or invalid
 The error message is: ('EOF in multi-line string', (205, 187))
 [...]
 RuntimeError: ECL says: THROW: The catch MACSYMA-QUIT is undefined.
 }}}
 looking at the commit more carefully, one sees renaming
 {{{to_poly_solver}}} to {{{to_poly_solve}}}.
 If I make this change in sage/interfaces/maxima_lib.py, line 142, the
 error go away. So in fact these {{{?integer?}}} things got in later.

 Back to {{{git bisect}}} now.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13364#comment:92>
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