On Sep 7, 2010, at 03:09 , Jeroen Demeyer wrote:
Hello sage-devel,
As far as we know, there are no more remaining issues for the PARI
update (#9343). We haven't had any doctest failures for a while now.
The main issues recently have been with PARI not compiling properly on
various machines,
On Tue, 07 Sep 2010 at 12:09PM +0200, Jeroen Demeyer wrote:
In order to test this thoroughly, extract the tarball and then:
cd sage-4.6.prealpha4
make
env SAGE_CHECK=yes SAGE_TUNE_pari=yes ./sage -f
pari-2.4.3.svn-12577.p5.spkg
make ptestlong
Another data point: with the above
On Tue, 07 Sep 2010 at 12:09PM +0200, Jeroen Demeyer wrote:
As far as we know, there are no more remaining issues for the PARI
update (#9343). We haven't had any doctest failures for a while now.
The main issues recently have been with PARI not compiling properly on
various machines, but all
On 09/ 8/10 09:57 AM, Dan Drake wrote:
I do get intermittent failures when I run make ptestlong; the doctest
will fail with something like this:
sage -t -long devel/sage/sage/structure/proof/all.py
python: can't open file '/home/drake/.sage//tmp/all.py': [Errno 2] No
such file
On 09/ 7/10 11:09 AM, Jeroen Demeyer wrote:
Hello sage-devel,
As far as we know, there are no more remaining issues for the PARI
update (#9343). We haven't had any doctest failures for a while now.
The main issues recently have been with PARI not compiling properly on
various machines, but all
Hello sage-devel,
As far as we know, there are no more remaining issues for the PARI
update (#9343). We haven't had any doctest failures for a while now.
The main issues recently have been with PARI not compiling properly on
various machines, but all those seem to be fixed now.
I have made a