#9343: Upgrade PARI to svn snapshot 12577 - a pre-release of PARI 2.4.3.
---------------------------------------------------------------------------------------------------------------------------+
   Reporter:  was                                                               
                                           |       Owner:  jdemeyer  
       Type:  enhancement                                                       
                                           |      Status:  needs_work
   Priority:  blocker                                                           
                                           |   Milestone:  sage-4.6  
  Component:  packages                                                          
                                           |    Keywords:            
     Author:  Robert Bradshaw, John Cremona, Jeroen Demeyer, William Stein, 
David Kirkby                                   |    Upstream:  N/A       
   Reviewer:  Robert Bradshaw, John Cremona, Jeroen Demeyer, William Stein, 
David Kirkby, François Bissey, Leif Leonhardy  |      Merged:            
Work_issues:                                                                    
                                           |  
---------------------------------------------------------------------------------------------------------------------------+

Comment(by leif):

 Replying to [comment:328 jdemeyer]:
 > Replying to [comment:327 leif]:
 > > Should we open a new ticket for issues with MPIR 2.1.1 (#8664) and ECM
 6.3 (#5847)?
 > >
 > > (Both currently need review, work for me with 4.5.3.alpha2, but not
 fully with 4.6.prealpha3 [segfault in
 {{{sage/schemes/elliptic_curves/ell_point.py}}}].)
 >
 > Any idea which patch from 4.6.prealpha3 could cause this?

 Nope. I'm not competent to track this down. But since the file containing
 the failing example also has a 9343-patched doctest (different ''result''
 only), the code obviously (indirectly) uses PARI.

 > I don't think MPIR or ECM depends on PARI/GP.

 No, but the code depends on them.

 I guess John C. will know. I just wonder ''where'' we should address such
 issues; #8664 (with #5847 mandatory) is likely to go into the 4.6 series.
 (Though perhaps not 4.6.0, I'm not the release manager.)

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