#7377: Symbolic Ring to Maxima via EclObject
-----------------------------------------------------------------------+----
   Reporter:  nbruin                                                   |       
Owner:  nbruin      
       Type:  enhancement                                              |      
Status:  needs_work  
   Priority:  major                                                    |   
Milestone:  sage-feature
  Component:  symbolics                                                |    
Keywords:              
     Author:  Nils Bruin, Jean-Pierre Flori                            |    
Upstream:  N/A         
   Reviewer:  Jean-Pierre Flori, François Bissey, Karl-Dieter Crisman  |      
Merged:              
Work_issues:                                                           |  
-----------------------------------------------------------------------+----

Comment(by nbruin):

 Replying to [comment:64 jpflori]:
 > It kind of works easily thanks to the current Method Resolution Order
 used by the version of Python in Sage but it obviously introduces a lot of
 new failures in addition to the one above.

 Perhaps you can do a quick test if depending on multiple inheritance
 causes a huge slowdown in method resolution? (I guess that is the only
 major architectural change you're making). Since it's the *proper* thing
 to do even a small slowdown should be acceptable, but we wouldn't want to
 degrade too badly.

 > The patch must be applied after the "_p2" patches (and ecl_iter).

 I recommend that you first do the refactoring *without* fast-calculus.
 That basically takes maxima_lib out of the equation and means you'll be
 refactoring code that is known to be good (actually, a quick test seems to
 indicate that the pexpect maxima interface based on abstract_maxima
 already breaks doctests. I think that back in 4.1.* or whatever Robert's
 work was based on, they were fine, so there may be some changes that
 didn't properly get adapted for the _p2 patches).

 Perhaps open a separate ticket "refactor maxima to multiply inherit from a
 new class maxima_abstract and pexpect". It would reduce the number of
 complicating factors you'd be considering.

 Work here would basically remain exploratory until that ticket is
 finished. We can then rebase the work here to your new organization of
 maxima interfaces. I noticed that your changes to maxima_lib.py were
 minimal so at least for now, that should be easy.

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