New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Sage compatible with PARI stable and PARI master #23796
Comments
Branch: u/jdemeyer/ticket/23796 |
Commit: |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:6
Looks good to me. Passes basic tests. |
Reviewer: Francois Bissey |
comment:7
Thanks! I hope this helps. |
Changed reviewer from Francois Bissey to François Bissey |
comment:8
On 32-bit:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:10
Obvious fix. |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. This was a forced push. New commits:
|
comment:14
Pending because of upstream discussion at sagemath/cypari2#38 |
comment:15
OK, the |
comment:16
Because you had left the ticket on positive review Volker already included it in his current merge, we can expect it to be closed fixed in his next round of closure - unless some new problem crop up. |
Changed branch from u/jdemeyer/ticket/23796 to |
This makes a few changes to Sage to allow it to be compatible with both PARI stable 2.9.3, as well as PARI git master (see #23544).
With "compatible", I mean that Sage builds and that all doctests are mathematically correct. So, doctests might fail but only because one correct answer is replaced by a different correct answer.
The main change is one call to
ellwp()
, where the current PARI version returns a value which is a factor 2 too small. Interestingly, Sage compensates for this by using a wrong formula later, to get correct results anyway.CC: @infinity0 @kiwifb @JohnCremona
Component: packages: standard
Author: Jeroen Demeyer
Branch/Commit:
c214994
Reviewer: François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/23796
The text was updated successfully, but these errors were encountered: