I know this is late, but all tests passed and the build went fine on
my work machine, which runs amd64 hardy heron.


On Tue, Nov 11, 2008 at 7:24 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
> Hello folks,
>
> here is 3.2.rc0 and I have to confess that I cheated: I did build this
> on numerous platforms before announcing here (if you hung out in IRC
> you knew about this release for about 6 hours now) and as it turns out
> my caution was justified. Doctesting is broken with this release
> unless you do the following:
>
>  ./sage -sh
>  cd local/bin
>  hg update -C
>
> After doing that doctesting works again. The issue is (again) releated
> to -sdist and I should have a fix in rc1 shortly. The initial plan has
> been shifted by about 5 days, so expect a releae by Thursday. We
> merged some major features in rc0, specifically the new timeit doctest
> code as well as Cython 0.10 and the RDF/CDF backend switch to numpy.
> Expect some numerical noise doctest failures and some other related
> known issues. Please report issues here and check trac for existing
> tickerts. There was also some major setup.py surgery, so please report
> any Sage library build issue. "sage -b" should be much faster and less
> buggy than before, but .... ;) One issue you will see  here is that we
> no longer suppress warnings, so expect "sage -b" to be more noise.
> While most of those are caused by Cython's code generator due to
> unused variables there is definitely some stuff in there worth fixing.
> If the noise level is too annoying we can turn on warning suppression
> by default again.
>
> Sources and a sage.math only binary can be found at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2/
>
> Cheers,
>
> Michael
>
> Merged in Sage 3.2.rc0:
>
> #3310: Craig Citro,  Gonzalo Tonaria: sage -b fails after touching
> sage/libs/mwrank/{mwrank.pyx,wrap.cc} [Reviewed by Michael Abshoff]
> #3476: Nick Alexander, Mike Hansen: save timeit information with sage -
> t -timeit [Reviewed by Mike Hansen, Michael Abshoff]
> #3498: Jason Grout: make numpy the backend for matrices over CDF and
> RDF [Reviewed by Mike Hansen, Robert Bradshaw, Michael Abshoff]
> #3580: Craig Citro, John Voight: ensure that totallyreal does not
> import numpy on startup [Reviewed by John Voight, Craig Citro]
> #3750: Karl-Dieter Crisman: Request for a "log" function for Sage
> integers [Reviewed by Mike Hansen]
> #4362: Dan Bump: Bug fixes in tableaux latex output [Reviewed by Mike
> Hansen, Nicolas Thiery]
> #4395: William Stein: Sage 3.1.4: magma related optional doctest
> failure in sage/rings/quotient_ring.py [Reviewed by Michael Abshoff]
> #4425: Karl-Dieter Crisman: sqrt(4) returns a SymbolicComposition
> instead of the number 2! [Reviewed by William Stein]
> #4443: Craig Citro: Massive prime_range speedup, arith* files cleanup
> [Reviewed by John Cremona]
> #4444: Craig Citro: Remove duplicate source names in setup.py
> [Reviewed by Michael Abshoff]
> #4448: Jason Grout: bug in interact with matrices [Reviewed by Mike
> Hansen]
> #4452: William Stein: optimize next_prime [Reviewed by Robert
> Bradshaw]
> #4455: Nicolas Thiery: bug in Coxeter matrix for type G2 [Reviewed by
> Mike Hansen]
> #4462: John Perry, Jason Grout: contour_plot defaults changed to fill,
> affects implicit_plot [Reviewed by Mike Hansen]
> #4467: Michael Abshoff: removed unused hanke library code [Reviwed by
> Jon Hanke]
> #4473: William Stein: loading file.sage that has a line "load foo.py"
> is broken due to a missing import [Reviewed by Michael Abshoff]
> #4476: Robert Bradshaw: Update to Cython 0.10 [Reviewed by Michael
> Abshoff]
> #4479: Timothy Clemans: sage/logic/logic.py contains a trivial typo: "
> varaiable" [Reviewed by Minh Nguyen]
> >
>

--~--~---------~--~----~------------~-------~--~----~
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://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to