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

Comment(by jpflori):

 A new spkg is available at http://perso.telecom-
 paristech.fr/~flori/sage/pynac-0.2.1.p0.spkg .

 I just updated SPKG.txt and commited the changeset in comparison with
 pynac-0.2.1-patched.spkg .

 The changes i pynac code from 0.2.1 are the result of applying:

  1.
 
[http://trac.sagemath.org/sage_trac/attachment/ticket/9880/trac9880_pynac_order_burcin_original.patch
 trac9880_pynac_order_burcin_original.patch]
  1.
 
[http://trac.sagemath.org/sage_trac/attachment/ticket/9880/trac_9880-pynac_order_jp_new-p2.patch
 trac_9880-pynac_order_jp_new-p2.patch]

 If you want to have access to the comparison functions used by the
 printing order (to stress pynac with Volker code
 [http://trac.sagemath.org/sage_trac/attachment/ticket/9880/strict_weak_order.py
 strict_weak_order.py] for example) you must also apply the patch
 access_order.patch .

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