#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:355 cremona]:
> I lost track of who is doing what, so I don't know what (or who) we are
waiting for. Or who will be the one to actually give it a positive
review.
Me, too. Also, it looks as if there was a lack of (other, "independent")
reviewers, or at least people testing this. I still don't know if this has
been tested on Cygwin, and, if there were any issues, if we should address
them ''here''. (Mike has provided a "follow-up" Lcalc to make it work on
Cygwin; I'm not sure if that's the only required change w.r.t. prealpha3.)
> Presumably what we want is that as soon as 4.5.3 is released the current
prealpha of 4.6 is released as an alpha?
I actually expected a 4.5.3 release candidate rather than an alpha2, and
4.5.3 released earlier. 4.6.prealpha3 is still based on 4.5.3.alpha1, but
as far as I know the only changes in 4.5.3.alpha2 are fixing numerical
noise in doctests, and #9722, which I am porting to the new PARI; Mitesh
will know better.
> What is to stop that happening now?
Regarding this ticket, the only things I'm aware of are:
* preparing a PARI 2.4.3.svn-12577.p5 spkg, with the fixes from #9722,
and in addition disabling the use of GMP internals by PARI by default
(with an ''option'' to make PARI use them)
* fixing Sphinx warnings
* adding more documentation (strings) and doctests to (at least)
{{{sage/libs/pari/gen.pyx}}} (cf.
[http://trac.sagemath.org/sage_trac/ticket/9343#comment:250 this comment]
and the [http://trac.sagemath.org/sage_trac/attachment/ticket/9343/pari-
gen.pyx-coverage.txt corresponding attachment]).
I don't know if further (new?) PARI functions should be wrapped; I only
came across the deprecated {{{orderell()}}}.
IMHO other things (e.g. Lcalc spkg improvements; I've commented on Mike's
follow-up #9775) should be addressed during the normal 4.6 release cycle.
I guess an official 4.6.alpha would be tested by far more people, on a
broader variety of systems. Same for 4.5.3 (final). If any problems arise
with the latter, they should be fixed during the preparation of 4.6
alphas, not in our inofficial prealphas.
Replying to [comment:356 jdemeyer]:
> [...] port #9722 to #9343. I believe leif is working on that.
Yes. Unfortunately the MPIR 2.1.1 issue took too much of my time and
resources; I now consider it (more or less) "resolved", and continue the
work on the PARI 2.4.3.svn-12577.p5 spkg.
> The large number of doctests without errors for sage-4.6.prealpha3 seem
to indicate that the patches are fine.
Hopefully. It might also indicate a lack of (appropriate) doctests... ;-)
(E.g., despite the obvious bug in MPIR 2.1.1, Sage 4.5.3.alpha2 and
4.6.prealpha3 - with PARI ''not'' using GMP internals - both passed all
long tests on two systems with it. There have been similar cases in the
past.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9343#comment:357>
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.
