On 25 Jul 2017 21:16, "Jeroen Demeyer" <[email protected]> wrote: > > Hello sage-devel and sage-packaging, > > I propose to upgrade the PARI package to the git master version instead of the current released version. > > > A second motivation is that stable releases of PARI are very slow. The most recent stable PARI releases (excluding bugfix releases) were in november 2016, march 2014 and june 2011. Upgrading now to git master gives the advantage that we can profit from improvements in PARI. It will also make the transition to the next stable release easier: the large time between stable releases implies many changes. Since many components of Sage use PARI, there are a substantial number of changes needed in Sage with every PARI upgrade. By doing this upgrade in steps, this becomes more manageable. > > I do know that this request is controversial because distributions are not likely to accept a "git master" version. However, I feel that I cannot make progress with the PARI Jupyter kernel unless this is resolved. So I would like distributions to accept that Sage is moving again to a git master version of PARI.
> I didn't make a Trac ticket for this yet precisely because I know it is controversial. > > Comments? Suggestions? > Jeroen. Would it be worth creating a fork of PARI, where the fork just puts out a stable release when needed? Call is Sage-PARI or something, then you would avoid the problems of a distribution not accepting a git-master copy. Dave -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
