Sage 8.8.rc3 released

154 views
Skip to first unread message

Volker Braun

unread,
Jun 23, 2019, 2:23:36 PM6/23/19
to sage-release
As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 

b03c9ca80c (tag: 8.8.rc3) Updated SageMath version to 8.8.rc3
2a9de2333b Trac #28042: broken arithmetic over GF(p)
4d1cf508f9 Trac #28036: Fix infinite loop from #21161 - repr of NumberFields (the parents) should indicate its embedding if there is one
8084b69595 (tag: 8.8.rc2) Updated SageMath version to 8.8.rc2

darwin doppelganger

unread,
Jun 23, 2019, 8:40:24 PM6/23/19
to sage-release
I just successfully finished building SageMath version 8.8.rc3 on my MacBook Pro, Mojave 10.14.4, Xcode 10.2.1.

Eric Gourgoulhon

unread,
Jun 24, 2019, 7:52:11 AM6/24/19
to sage-release
On Ubuntu 18.04 running on bi-Xeon E5-2623 (8 cores) + 16 GB RAM:

- python2:

  - incremental build (from 8.8.rc2, with -j16) completed, with Sphinx complaining during the doc build:
     formatargspec() is now deprecated.  Please use sphinx.util.inspect.Signature instead

  - all tests from ptestlong passed

- python3:

  - incremental build (from 8.8.rc2, with -j16) completed, with the same Sphinx deprecation warning as with python 2.

  - tests from ptest-python3 passed, except for 2 doctests
    in src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py:

sage -t --long --warn-long 50.3 src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py
**********************************************************************
File "src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py", line 1372, in sage.schemes.hyperelliptic_curves.hyperelliptic_finite_field.HyperellipticCurve_finite_field.zeta_function
Failed example:
    H = HyperellipticCurve(t^5 + a*t)
Exception raised:
    Traceback (most recent call last):
      File "/home/eric/sage/py3/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 681, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/home/eric/sage/py3/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 1105, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.schemes.hyperelliptic_curves.hyperelliptic_finite_field.HyperellipticCurve_finite_field.zeta_function[7]>", line 1, in <module>
        H = HyperellipticCurve(t**Integer(5) + a*t)
      File "/home/eric/sage/py3/local/lib/python3.7/site-packages/sage/schemes/hyperelliptic_curves/constructor.py", line 220, in HyperellipticCurve
        raise ValueError("In characteristic 2, argument h (= %s) must be non-zero."%h)
    ValueError: In characteristic 2, argument h (= 0) must be non-zero.
**********************************************************************
File "src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py", line 1373, in sage.schemes.hyperelliptic_curves.hyperelliptic_finite_field.HyperellipticCurve_finite_field.zeta_function
Failed example:
    H.zeta_function()
Expected:
    (81*x^4 + 72*x^3 + 32*x^2 + 8*x + 1)/(9*x^2 - 10*x + 1)
Got:
    (16*x^4 + 8*x^3 + x^2 + 2*x + 1)/(4*x^2 - 5*x + 1)
**********************************************************************
1 item had failures:
   2 of  16 in sage.schemes.hyperelliptic_curves.hyperelliptic_finite_field.HyperellipticCurve_finite_field.zeta_function
    [373 tests, 2 failures, 59.91 s]

The 2 doctests are passed when run standalone.

NB: these are the same errors as with 8.8.rc2 and, IIRC, as with 8.8.rc1. So it seems the errors are reproducible when doctesting with "make ptest-python3". They are not directly related to parallel doctesting though, since

./sage -tp --long --warn-long 50.3 src/sage/schemes/

yields

Running doctests with ID 2019-06-24-13-52-38-4df2b045.
Git branch: develop
Using --optional=build,dochtml,memlimit,mpir,python2,sage
Sorting sources by runtime so that slower doctests are run first....
Doctesting 144 files using 8 threads.
...
----------------------------------------------------------------------
All tests passed!
----------------------------------------------------------------------
Total time for all tests: 139.5 seconds
    cpu time: 930.2 seconds
    cumulative wall time: 1003.4 seconds

Eric.

François Bissey

unread,
Jun 25, 2019, 11:17:37 PM6/25/19
to 'Justin C. Walker' via sage-release
Unless we are ready to ship 8.8 with broken pdf docs I created
https://trac.sagemath.org/ticket/28059
and marked it as a blocker. Feel free to downgrade the severity
if you think it is appropriate.

François
> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To post to this group, send email to sage-r...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-release.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/aebd284b-ff4a-44a1-8a15-1f7e4816bba1%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Volker Braun

unread,
Jun 26, 2019, 1:03:34 PM6/26/19
to sage-release
IMHO the main point of the pdf docs is to check that the LaTeX math is valid, nobody is going to download and print the pdf docs (i hope). So no blocker....

> To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.

François Bissey

unread,
Jun 26, 2019, 4:59:43 PM6/26/19
to 'Justin C. Walker' via sage-release
Print no. But I have users of sage-on-gentoo who have told me that they find it handy
and consult it from their phone and stuff.

Vincent Delecroix

unread,
Jun 26, 2019, 5:25:31 PM6/26/19
to sage-r...@googlegroups.com
+1

Some users reported that they prefer reading pdf rather than html.

Samuel Lelievre

unread,
Jun 28, 2019, 11:03:44 AM6/28/19
to sage-release
Also, pdf chapters of the SageMath documentation tend
to rank quite high among results for web search engine
queries about Sage.
Reply all
Reply to author
Forward
0 new messages