#9880: Segfault in PyNaC 0.2.0.p4
-------------------------+--------------------------------------------------
   Reporter:  jpflori    |       Owner:  burcin      
       Type:  defect     |      Status:  needs_review
   Priority:  major      |   Milestone:  sage-4.6.1  
  Component:  symbolics  |    Keywords:  pynac       
     Author:             |    Upstream:  N/A         
   Reviewer:             |      Merged:              
Work_issues:             |  
-------------------------+--------------------------------------------------

Comment(by jpflori):

 I guess there are two main parts in this ticket, I did not have a look for
 a long time, so all this should be taken carefully :

 - Burcin patch which (more or less) revert the internal ordering in Pynac
 to the original one in Ginac and create new methods to use a different
 order for printing. We could maybe only apply the part reverting the
 internal order to Ginac original one to get the bug solved and close this
 ticket.

 - However, it is not a solution to use Ginac order for printing because it
 is quite random and unpredictable, it depends on variable order creation
 among others. That's the reason for the different order for printing (and
 getting operands and so on). It was not quite coherent, whence my patch to
 make it a little better. We could merge that in a second ticket. By the
 way, the order implemented right now should be more or less degrevlex.

 - With that new framework, we could also quite easily allow the use of
 different orders for manipulating (ie printing, getting operands...)
 symbolic expressions in Sage (Burcin already mentionned that somewhere on
 the Web IIRC).

 - I think there is still work to do regarding expressions manipulation
 (see #9989)

 - I don't really have an idea of what could get misprinted with Burcin+my
 patch applied. You could try multivariate polynomials to check it follows
 degrevlex, then such expressions times exponentials and let me know what
 you feel.[[BR]]

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