#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):

 Replying to [comment:90 leif]:
 > Same happens with just `./sage -t ...` or `make test[long]`, i.e. non-
 parallel?
 >
 > We had strange errors with `ptest[long]` or `./sage -tp N ...` when
 `SAGE_PATH` was set (even to the empty string).

 That is not set:
 {{{
 jec@fermat%env | grep SAGE
 SAGE_PARALLEL_SPKG_BUILD=yes
 }}}

 make testlong was no better, neither is testing a single file (e.g. ./sage
 -t devel/sage/sage/rings/infinity.py).  Sage does start up properly.

 Looking at the actual error message (why not?) I see that it complains
 that the line
 {{{
 from sage.all_cmdline import *;
 }}}
 which is presumably included in the testing framework, causes
 sage.all_cmdline.py to be imported, and then in line 24 of that file the
 line 24:
 {{{
    raise ValueError, msg
 }}}
 raises the error, with the message coming from a few lines above where
 there is a try/except block containing
 {{{
     from sage.all import *
     from sage.calculus.predefined import x
     preparser(on=True)
 }}}
 and this is causing some kind of circular import.

 Anyway, by 4.7 build which I have been using for weeks, and which passed
 all the tests when I built it, now gives rise to exactly the same problem.
 So this is nothing to do with any of the code on this ticket, but instead
 something weird that has happened with my Sage installations.

 Here's an idea: I have several background jobs running sage;  is it
 possible that this is the problem?  They will also be writing to ~/.sage.
 I'll try again when they have finished.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11130#comment:91>
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.

Reply via email to