On 25/07/2017 22:44, Jeroen Demeyer wrote:
On 2017-07-25 22:34, Ximin Luo wrote:
Do you think it would be feasible for Sage "standard" to maintain
compatibility with both PARI stable and the development version?
I have not actually tried, so it is hard to tell right now.
Given the past history of the PARI package inside Sage, I expect that we
will regularly upgrade PARI in Sage to future git master versions. Every
time, the difference with the stable version increases and the chance of
compatibility decreases. So even if we are compatible now, there is no
guarantee that this will remain the case in the future. Moreover, we do
not have machinery in place to check this compatibility: I can do it for
this upgrade, but it might easily be forgotten the next time.
For sure we could and must maintain the compatibility of cypari2 with
both the last(s) pari stable and pari master. Sage uses mostly pari
through this cypari2 interface. Because of this, it might not be so hard
to have Sage built with various PARI versions.
The travis script in cypari2 can be updated to test several pari releases.
Everything also depends on how you define "compatibility". There might
be a large difference between "Sage builds and works" and "all doctests
pass". The first one is much more likely than the second one.
Vincent
--
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
