#11130: Update PARI to version 2.5.0
--------------------------------------------+-------------------------------
Reporter: jdemeyer | Owner: jdemeyer
Type: defect | Status: needs_review
Priority: critical | Milestone: sage-4.7.2
Component: packages | Keywords: pari spkg
Work_issues: | Upstream: N/A
Reviewer: John Cremona, Jeroen Demeyer | Author: Jeroen Demeyer,
John Cremona
Merged: | Dependencies: #11230, #11234,
#11321 (install this '''after''' building PARI)
--------------------------------------------+-------------------------------
Comment(by cremona):
Starting with a clean 4.7.1.rc1 (I think) I successfully applied both
spkgs (using SAGE_CHECK=yes) and 5 patches to sagelib and 1 to
data/extcode, and did sage -ba.
Sage now starts up OK but I'm having a lot of problems with any more
testing. For example, moving into devel/sage and doing "../../sage -tp 20
./sage" results in very many errors, looks like in every file, like this:
{{{
Traceback (most recent call last):
File "/home/jec/.sage//tmp/facade_sets.py", line 2, in <module>
from sage.all_cmdline import *;
File "/home/jec/sage-4.7.1.rc1/local/lib/python/site-
packages/sage/all_cmdline.py", line 24, in <module>
raise ValueError, msg
ValueError: Attempted relative import in non-package
}}}
I checked (using bash's history) that I had remembered to hg qpush each
patch.
Does this make any sense? I suppose I could rebuild 4.7.1.rc1 from
scratch.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11130#comment:78>
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.
