Sage 9.0 released

312 views
Skip to first unread message

Volker Braun

unread,
Jan 1, 2020, 7:15:15 AM1/1/20
to sage-release
Just in time for the new decade, here is the first version of Sage running on Python 3 by default. Many thanks to everyone who contributed! 

The "master" git branch has been updated to Sage-9.0. 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

There was no change over 9.0.rc1

Jaap Spies

unread,
Jan 1, 2020, 7:21:09 AM1/1/20
to sage-r...@googlegroups.com
Congrats! And many thanks!

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/77b461ee-11e3-4678-9058-d0a37237f3a4%40googlegroups.com.

Kwankyu Lee

unread,
Jan 1, 2020, 10:17:06 AM1/1/20
to sage-release
Wow! I would take the honour to be the second person to celebrate the release of Sage on Python 3 by default.

I thank the great people in the Sage developer community who made this!

A nice present for the new year!

Eric Gourgoulhon

unread,
Jan 1, 2020, 2:29:58 PM1/1/20
to sage-release
Thank you very much Volker!
And congratulations to all people who made the Python 3 switch possible, especially to Frédéric Chapoton!
Happy New Year!

Eric.


Nicolas M. Thiery

unread,
Jan 1, 2020, 2:43:53 PM1/1/20
to sage-r...@googlegroups.com

Deep bow indeed to Frédéric for leading the Python 3 charge!

And to everyone else for making it possible.

And to Volker for yet another release management, right on time for
Python3's 2020 pledge :-)

Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <nth...@users.sf.net>
http://Nicolas.Thiery.name/

Emmanuel Charpentier

unread,
Jan 1, 2020, 5:45:51 PM1/1/20
to sage-release
Congratulations ! And atriple ban four the release manager, who managed to get a Python 3-base Sage just in time. Kudos...


Le mercredi 1 janvier 2020 13:15:15 UTC+1, Volker Braun a écrit :
Just in time for the new decade,

Mandatory nitpick: the second decade of the 21ts century CE shall end on Dec 31, 2020 23:59:59. As it has already been noted, there is no year 0 in this calendar : the latter predates the introduction of the concept of a number zero ; furthermore, mathematics were not the forte of (most of) the ecclesiastics who created this calendar (they even managed to slip in an offset in the calendar : the historical events supposed to take place around the birth of the person identified as Jesus of Nazareth point this birth around 5 BC. Nice Irishism...).

This is probably the most common off-by-one (fencepost) error in all mathematics and programming. We are stuck with it ; we can at least try to be consistent...

HTH (but not really expecting TH),

Emmanuel Charpentier

unread,
Jan 1, 2020, 7:57:24 PM1/1/20
to sage-release

On Debian testing running on core i7 + 16 GB RAM after upgrading a Python 3-based 9.0.rc0 to 9.0, ptestalllong gets 7 transient and 3 permanent failures:

File Result P/T
src/sage/symbolic/integration/external.py 1 doctest failed T
src/sage/interfaces/psage.py 1 doctest failed T
src/sage/modular/ssmod/ssmod.py 2 doctests failed T
src/sage/plot/animate.py 7 doctests failed T
src/sage/numerical/backends/glpk_backend.pyx 1 doctest failed P
src/sage/tests/gap_packages.py 1 doctest failed P
src/sage/misc/latex.py 1 doctest failed T
src/sage/libs/glpk/error.pyx 1 doctest failed P
src/sage/repl/load.py 1 doctest failed T
src/sage/databases/findstat.py 8 doctests failed T

All these failures have already been reported for previous betas.

HTH,

Le mercredi 1 janvier 2020 13:15:15 UTC+1, Volker Braun a écrit :

Justin C. Walker

unread,
Jan 1, 2020, 9:49:37 PM1/1/20
to 'Justin C. Walker' via sage-release


> On Jan 1, 2020, at 04:15 , Volker Braun <vbrau...@gmail.com> wrote:
>
> Just in time for the new decade, here is the first version of Sage running on Python 3 by default. Many thanks to everyone who contributed!

+1, and thanks for all your hard work!

> The "master" git branch has been updated to Sage-9.0. 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

Just for the record: Built from a fresh clone of the develop tree, on two macOS systems: 10.13.6 (2017 iMac Pro, 18-core Xeon W) and 10.14.6 (2017 MBP, Quad-core Core i7). No problems with the build, and all tests (‘ptestlong’) passed on both systems!

Justin

--
Justin C. Walker, Curmudgeon at Large
Director
Institute for the Enhancement of the Director's income
-----------
--
They said it couldn't be done, but sometimes,
it doesn't work out that way.
- Casey Stengel
--



kcrisman

unread,
Jan 2, 2020, 10:06:05 AM1/2/20
to sage-release


On Wednesday, January 1, 2020 at 5:45:51 PM UTC-5, Emmanuel Charpentier wrote:
Congratulations ! And atriple ban four the release manager, who managed to get a Python 3-base Sage just in time. Kudos...

Le mercredi 1 janvier 2020 13:15:15 UTC+1, Volker Braun a écrit :
Just in time for the new decade,

Mandatory nitpick: the second decade of the 21ts century CE shall end on Dec 31, 2020 23:59:59. As it has already been noted, there is no year 0 in this calendar :

Emmanuel Charpentier

unread,
Jan 2, 2020, 11:38:39 AM1/2/20
to sage-release
;-] 

Why should I accept this "authority" and sacrifice consistency ? ;-)...
 

Frédéric Chapoton

unread,
Jan 2, 2020, 11:40:54 AM1/2/20
to sage-release
Several people, including me on several machines, seem to have issues when building the R 3.6.2 package. See


This was already discussed in the thread of 9.0.rc1.

F


Le mercredi 1 janvier 2020 13:15:15 UTC+1, Volker Braun a écrit :

Thierry Dumont

unread,
Jan 2, 2020, 8:01:56 PM1/2/20
to Frédéric Chapoton, sage-r...@googlegroups.com

On my Ubuntu 19:10 (the last one!);  I could not upgrade to 9.0, due to this "R" problem.

So, I have deleted my sage tree (sniff) and cloned a fresh one. After that everything went ok. There should be dependence

problems with some libraries.

Yours

t.

--
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.
tdumont.vcf

Isuru Fernando

unread,
Jan 2, 2020, 10:48:22 PM1/2/20
to sage-r...@googlegroups.com
Just built conda packages for sage 9.0 and there's only 33 doctests failing down from 36 for 8.9.

Isuru

Volker Braun

unread,
Jan 3, 2020, 7:44:50 PM1/3/20
to sage-release
Binaries are up now!

John Cremona

unread,
Jan 4, 2020, 6:49:23 AM1/4/20
to sage-release
Building from source from scratch on ubuntu 16.04 I had a problem:

Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: python3-3.7.3.p1
  log file: /usr/local/sage/sage-9.0/logs/pkgs/python3-3.7.3.p1.log
  build directory: /usr/local/sage/sage-9.0/local/var/tmp/sage/build/python3-3.7.3.p1

(log attached).   The machines does have python3 installed system-wide.

John

On Saturday, January 4, 2020 at 12:44:50 AM UTC, Volker Braun wrote:
Binaries are up now!
python3-3.7.3.p1.log

John Cremona

unread,
Jan 4, 2020, 12:30:54 PM1/4/20
to sage-r...@googlegroups.com
On Sat, 4 Jan 2020 at 11:49, John Cremona <john.c...@gmail.com> wrote:
Building from source from scratch on ubuntu 16.04 I had a problem:

Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: python3-3.7.3.p1
  log file: /usr/local/sage/sage-9.0/logs/pkgs/python3-3.7.3.p1.log
  build directory: /usr/local/sage/sage-9.0/local/var/tmp/sage/build/python3-3.7.3.p1

(log attached).   The machines does have python3 installed system-wide.

I found the discussion at https://ask.sagemath.org/question/48276/building-sage-89-from-source-fails/  and installed libncurses5-dev, then tried ./sage -f python3 but it failed in the same way, so I am trying after make distclean; make configure; ./configure; make


 

John

On Saturday, January 4, 2020 at 12:44:50 AM UTC, Volker Braun wrote:
Binaries are up now!

--
You received this message because you are subscribed to a topic in the Google Groups "sage-release" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-release/OB5SKREDJts/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-release...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/32f66730-ce10-4496-995c-1d337b03efb6%40googlegroups.com.

John Cremona

unread,
Jan 4, 2020, 12:34:34 PM1/4/20
to sage-r...@googlegroups.com
On Sat, 4 Jan 2020 at 17:30, John Cremona <john.c...@gmail.com> wrote:


On Sat, 4 Jan 2020 at 11:49, John Cremona <john.c...@gmail.com> wrote:
Building from source from scratch on ubuntu 16.04 I had a problem:

Error building Sage.

The following package(s) may have failed to build (not necessarily
during this run of 'make all-start'):

* package: python3-3.7.3.p1
  log file: /usr/local/sage/sage-9.0/logs/pkgs/python3-3.7.3.p1.log
  build directory: /usr/local/sage/sage-9.0/local/var/tmp/sage/build/python3-3.7.3.p1

(log attached).   The machines does have python3 installed system-wide.

I found the discussion at https://ask.sagemath.org/question/48276/building-sage-89-from-source-fails/  and installed libncurses5-dev, then tried ./sage -f python3 but it failed in the same way, so I am trying after make distclean; make configure; ./configure; make

Apologies now I see that some of the earlier thread on this topic was started by me with similar issues (on a different machine).  I just don't remember such things these days.  The sooner I can find someone else to be sysadmin for the 8 or so machines I look after the better!

Samuel Lelièvre

unread,
Jan 4, 2020, 5:58:11 PM1/4/20
to sage-release
Sat 2020-01-04 17:34 UTC, John Cremona:
>
> Apologies now I see that some of the earlier thread on this topic
> was started by me with similar issues (on a different machine).
> I just don't remember such things these days. The sooner I can
> find someone else to be sysadmin for the 8 or so machines
> I look after the better!

The error at the end of the log:

ModuleNotFoundError: No module named 'readline'

meant Python was not able to build its readline module.

So, did something like the following solve the problem?

$ sudo apt-get install libncurses5-dev libreadline-dev
$ make ncurses-clean
$ make readline-clean
$ make configure
$ ./configure
$ make

John Cremona

unread,
Jan 5, 2020, 7:01:55 AM1/5/20
to sage-r...@googlegroups.com
Yes it did -- thanks.  In fact I did "make distclean" instead of the first two lines as I was in no hurry (and te machine has 32 cores but was otherwise idle).

I am still working on two of my (ubuntu 16 LTS) machines which managed to build sage's python3 without openssl support.  I had the relevant python2 wrapper packages installed but not the python 3 ones, so I installed those and started again, no luck so far but I'll track it down by comparing log files across machines.  (Not having ssl support means that sage -pip install fails, as everyone knows, but which is not deemed to be a fatal failure of prerequisites.)

 

--
You received this message because you are subscribed to a topic in the Google Groups "sage-release" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-release/OB5SKREDJts/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-release...@googlegroups.com.

Sébastien Labbé

unread,
Jan 5, 2020, 12:22:48 PM1/5/20
to sage-release
Happy new year. Thank you very much Volker once again for the release. Thanks to all the people involved in the passage to Python3 including Frédéric Chapoton for the so many tickets he created, authored, reviewed to get Sage to work with Python 3.

Testing optional and external packages, I get

Using --optional=4ti2,cbc,ccache,cryptominisat,dot2tex,e_antic,external,glucose,latte_int,lidia,lrslib,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,rst2ipynb,sage,sagenb

----------------------------------------------------------------------
sage -t --long src/sage/databases/findstat.py  # 8 doctests failed
sage -t --long src/sage/databases/oeis.py  # 1 doctest failed
sage -t --long src/sage/geometry/polyhedron/base.py  # Killed due to abort
sage -t --long src/sage/graphs/generators/smallgraphs.py  # 2 doctests failed
sage -t --long src/sage/misc/latex.py  # 1 doctest failed
sage -t --long src/sage/plot/animate.py  # 7 doctests failed
sage -t --long src/sage/repl/load.py  # 1 doctest failed
----------------------------------------------------------------------
External software detected for doctesting: cplex,ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc

----------------------------------------------------------------------
sage -t --long src/sage/databases/findstat.py  # 8 doctests failed
sage -t --long src/sage/databases/oeis.py  # 1 doctest failed
sage -t --long src/sage/geometry/polyhedron/base.py  # Killed due to abort
sage -t --long src/sage/graphs/generators/smallgraphs.py  # 2 doctests failed
sage -t --long src/sage/misc/latex.py  # 1 doctest failed
sage -t --long src/sage/plot/animate.py  # 7 doctests failed
sage -t --long src/sage/repl/load.py  # 1 doctest failed
----------------------------------------------------------------------
External software detected for doctesting: ffmpeg,imagemagick,internet,latex

The oeis failure is copied below. Other are tracked at https://trac.sagemath.org/ticket/25536

sage -t --long src/sage/databases/oeis.py
**********************************************************************
File "src/sage/databases/oeis.py", line 53, in sage.databases.oeis
Failed example:
    c.comments()                                  # optional -- internet
Expected:
    0: The first 5,821,569,425 terms were computed by _Eric W. Weisstein_ on Sep 18 2011.
    1: The first 10,672,905,501 terms were computed by _Eric W. Weisstein_ on Jul 17 2013.
    2: The first 15,000,000,000 terms were computed by _Eric W. Weisstein_ on Jul 27 2013.
Got:
    0: The first 5821569425 terms were computed by _Eric W. Weisstein_ on Sep 18 2011.
    1: The first 10672905501 terms were computed by _Eric W. Weisstein_ on Jul 17 2013.
    2: The first 15000000000 terms were computed by _Eric W. Weisstein_ on Jul 27 2013.
**********************************************************************
1 item had failures:
   1 of  26 in sage.databases.oeis
    5 webbrowser tests not run
    0 tests not run because we ran out of time
    [281 tests, 1 failure, 36.32 s]

Emmanuel Charpentier

unread,
Jan 6, 2020, 11:21:35 AM1/6/20
to sage-release

On a slightly smaller machine (Debian testing running on core i5 + 8 GB RAM), after upgrading a Python 3-based 9.0.rc0 to 9.0, ptestalllong gets 11 transient failures (and no permanent failure):

Using --optional=build,dochtml,dot2tex,external,fricas,giacpy_sage,libsemigroups,memlimit,python2,sage,sagenb
File Result P/T
src/sage/databases/oeis.py 1 doctest failed T
src/sage/symbolic/integration/external.py 1 doctest failed T
src/sage/plot/animate.py 7 doctests failed T
src/doc/en/constructions/linearalgebra.rst 1 doctest failed T
src/sage/misc/latex.py 1 doctest failed T
src/doc/en/constructions/interfaceissues.rst 1 doctest failed T
src/sage/repl/load.py 1 doctest failed T
src/doc/en/developer/codinginother.rst 1 doctest failed T
src/sage/interfaces/octave.py 3 doctests failed T
src/sage/databases/findstat.py 55 doctests failed T
src/sage/interfaces/magmafree.py 2 doctests failed T
External software detected for doctesting: ffmpeg,graphviz,imagemagick,internet,latex,mathematica,octave,pandoc

HTH,

Reply all
Reply to author
Forward
0 new messages