alpha0 took ages longer than planned and I mostly blame this on the
fact that
I build 2.8.12 from source seven or eight times for various reasons.
It is a
long story, let's just leave it at that. So far alpha0 contains mostly
updated
spkgs and the spelling fixes by Paul and one modular symbols fix. I am
pushing
alpha0 out and keep working at alpha1, first merging Josh's updated
sympy and
numpy spkgs and then merging more refereed fixes. Alpha0 is at

http://sage.math.washington.edu/home/mabshoff/sage-2.8.13.alpha0.tar

at it is about 2 mb smaller since I removed some outdated spkgs :)

Thanks to all the reviewers, and please send me patches for the
doctest failures.

Cheers,

Michael

##################################################################

Merged spkgs:

#563: linbox-20070915.p2.spkg (Michael Abshoff)
#1029: flint-0.9.p0.spkg (Robert Bradshaw, Michael Abshoff)
#1126: libfplll-2.1.3-20071117.spkg (Martin Albrecht, Michael Abshoff)
#1152: sqlite-3.5.2.p1.spkg (Yi Qiang) [this might still get backed
out]
#1177: mpfr-2.3.0.p0.spkg (Michael Abshoff)
#1189: sympy-0.5.7.spkg (Ondrej Certik) [only the spkg, the patch has
been backed out]
#1197: cremona-20071116.spkg (John Cremona, William Stein, Ralf-Philip
Weinmann)
#1199: cvxopt-0.9.p1.spkg (Josh Kantor, Michael Abshoff, also #1121,
#1161)

Removed old spkgs:

pari-2.3.2.p3.spkg
gmp-4.2.1.p10.spkg
libpng-1.2.22.spkg

Things to check:

http://www.sagetrac.org/sage_trac/ticket/957 - is this still an issue?

Outstanding spkgs to be merged:

#1198: numpy-20071020.spkg (Josh Kantor)
#1198: scipy-20071020.spkg (Josh Kantor)

Josh has found a bug with the numpy install, so these will be in
alpha1.

##################################################################

ToDo:

bump python release number in case sqlite needs to be updated

I back out Ondrey's patch, the bit with corecion caused trouble all
over the map.

##################################################################

Failing doctests:

devel/sage-main/build/sage/databases/database.py
[sqlite update is most likely to blame]
devel/sage-main/sage/libs/flint/fmpz_poly.pyx
[Robert's flint-9.spkg didn't build of for me, so I fixed the NTL link
issue in p0]
devel/sage-main/sage/libs/cremona/constructor.py
[Not sure about that one. I merged:
[EMAIL PROTECTED]:/tmp/Work-mabshoff/release-cycles/sage-2.8.13.alpha0/
devel/sage$ ls -la /home/was/cremona/cremona*
-rw-r--r-- 1 was was 1430542 2007-11-17 22:28 /home/was/cremona/
cremona-20071116.spkg
-rw-r--r-- 1 was was   15350 2007-11-17 22:27 /home/was/cremona/
cremona.hg]

##################################################################
In detail:

sage -t  devel/sage-main/sage/libs/flint/fmpz_poly.pyx
**********************************************************************
File "fmpz_poly.pyx", line 271:
    sage: g / f
Exception raised:
    Traceback (most recent call last):
      File "/tmp/Work-mabshoff/release-cycles/sage-2.8.13.alpha0/local/
lib/python2.5/doctest.py", line 1212, in __run
        compileflags, 1) in test.globs
      File "<doctest __main__.example_13[3]>", line 1, in <module>
        g / f###line 271:
    sage: g / f
    TypeError: unsupported operand type(s) for /:
'sage.libs.flint.fmpz_poly.Fmpz_poly' and
'sage.libs.flint.fmpz_poly.Fmpz_poly'
**********************************************************************

sage -t  devel/sage-main/sage/libs/cremona/constructor.py
**********************************************************************
File "constructor.py", line 42:
    sage: M = CremonaModularSymbols(-1)
Expected:
    Traceback (most recent call last):
    ...
    ValueError: the level (= -1) must be a positive integer
Got:
    Traceback (most recent call last):
      File "/tmp/Work-mabshoff/release-cycles/sage-2.8.13.alpha0/local/
lib/python2.5/doctest.py", line 1212, in __run
        compileflags, 1) in test.globs
      File "<doctest __main__.example_0[4]>", line 1, in <module>
        M = CremonaModularSymbols(-Integer(1))###line 42:
    sage: M = CremonaModularSymbols(-1)
      File "/tmp/Work-mabshoff/release-cycles/sage-2.8.13.alpha0/local/
lib/python2.5/site-packages/sage/libs/cremona/constructor.py", line
64, in CremonaModularSymbols
        return ModularSymbols(level=level, sign=sign,
cuspidal=cuspidal, verbose=verbose)
      File "homspace.pyx", line 25, in
sage.libs.cremona.homspace.ModularSymbols.__init__
        raise ValueError, "the level (= %s) must be at least 2"%level
    ValueError: the level (= -1) must be at least 2
**********************************************************************
File "constructor.py", line 46:
    sage: M = CremonaModularSymbols(0)
Expected:
    Traceback (most recent call last):
    ...
    ValueError: the level (= 0) must be a positive integer
Got:
    Traceback (most recent call last):
      File "/tmp/Work-mabshoff/release-cycles/sage-2.8.13.alpha0/local/
lib/python2.5/doctest.py", line 1212, in __run
        compileflags, 1) in test.globs
      File "<doctest __main__.example_0[5]>", line 1, in <module>
        M = CremonaModularSymbols(Integer(0))###line 46:
    sage: M = CremonaModularSymbols(0)
      File "/tmp/Work-mabshoff/release-cycles/sage-2.8.13.alpha0/local/
lib/python2.5/site-packages/sage/libs/cremona/constructor.py", line
64, in CremonaModularSymbols
        return ModularSymbols(level=level, sign=sign,
cuspidal=cuspidal, verbose=verbose)
      File "homspace.pyx", line 25, in
sage.libs.cremona.homspace.ModularSymbols.__init__
        raise ValueError, "the level (= %s) must be at least 2"%level
    ValueError: the level (= 0) must be at least 2
**********************************************************************

./sage -t devel/sage-main/build/sage/databases/database.py
sage -t  devel/sage-main/build/sage/databases/database.py   sh: line
1: 18385 Segmentation fault      /tmp/Work-mabshoff/release-cycles/
sage-2.8.13.alpha0/local/bin/python .doctest_database.py >.doctest/out
2>.doctest/err


------------------------------------------------------------
Unhandled SIGSEGV: A segmentation fault occured in SAGE.
This probably occured because a *compiled* component
of SAGE has a bug in it (typically accessing invalid memory)
or is not properly wrapped with _sig_on, _sig_off.
You might want to run SAGE under gdb with 'sage -gdb' to debug this.
SAGE will now terminate (sorry).
------------------------------------------------------------


A mysterious error (perphaps a memory error?) occurred, which may have
crashed doctest.
         [1.6 s]
exit code: 256

----------------------------------------------------------------------

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to