Sage 8.1.rc3 released

246 views
Skip to first unread message

Volker Braun

unread,
Nov 23, 2017, 6:35:13 PM11/23/17
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

Unless #24085 is magically resolve real soon this shoud be the final rc...

20007d522c (tag: 8.1.rc3, trac/develop) Updated SageMath version to 8.1.rc3
010f8a5962 Trac #22851: Make qepcad experimental
a4f9804013 Trac #24238: add sympy as docbuild dependency
92f95cef93 (tag: 8.1.rc2) Updated SageMath version to 8.1.rc2

Emmanuel Charpentier

unread,
Nov 24, 2017, 3:32:40 AM11/24/17
to sage-release
Maybe have a look at Trac#24240 ?

Eric Gourgoulhon

unread,
Nov 24, 2017, 5:32:40 AM11/24/17
to sage-release
On Ubuntu 16.04 x86_64 Xeon E5-2623 + 16 GB RAM and from a fresh git clone + pull develop, parallel (-j16) build OK.
ptestlong is OK as well, modulo 1 transient doctest:

sage -t --long --warn-long 45.5 src/sage/manifolds/point.py  # 1 doctest failed

As usual on this computer since a few betas, this is due to the failure of Jmol to create some file in ~/.sage/temp/. This doctest is passed when run standalone. 

Best wishes,

Eric.





Eric Gourgoulhon

unread,
Nov 24, 2017, 5:38:07 AM11/24/17
to sage-release
Le vendredi 24 novembre 2017 11:32:40 UTC+1, Eric Gourgoulhon a écrit :

As usual on this computer since a few betas, this is due to the failure of Jmol to create some file in ~/.sage/temp/. This doctest is passed when run standalone. 

Btw, am I the only one in this case? The error message is
RichReprWarning: Exception in _rich_repr_ while displaying object: Jmol failed to create file '/home/eric/.sage/temp/tensor/13835/dir_vph5jK/preview.png', see '/home/eric/.sage/temp/tensor/13835/tmp_H7sQXZ.txt' for details
    Graphics3d Object

There is no file /home/eric/.sage/temp/tensor/13835/tmp_H7sQXZ.txt to see the details (probably it has been deleted before ptestlong was completed).
Also, it looks like a warning (RichReprWarning) which has been turned into an error....

Jeroen Demeyer

unread,
Nov 24, 2017, 6:01:21 AM11/24/17
to sage-r...@googlegroups.com
On 2017-11-24 11:38, Eric Gourgoulhon wrote:
> Btw, am I the only one in this case?

It seems so.

Dima Pasechnik

unread,
Nov 24, 2017, 12:32:22 PM11/24/17
to sage-release
Actually I think #24085 is fixed - pending final checks, but everything points in this direction for sure.

Justin C. Walker

unread,
Nov 24, 2017, 4:15:57 PM11/24/17
to sage-r...@googlegroups.com

> On Nov 23, 2017, at 15:35 , Volker Braun <vbrau...@gmail.com> wrote:
>
> 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
>
> Unless #24085 is magically resolve real soon this shoud be the final rc…

Built from a fresh clone of the developer branch, on macOS 10.11.6 (Quad-core Core i7), w/o problems.

Testing (‘ptestlong’) yielded no failures!

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Absorption of Federal Funds
--------
Men are from Earth.
Women are from Earth.
Deal with it.
--------



Georg Grafendorfer

unread,
Nov 26, 2017, 8:36:02 AM11/26/17
to sage-release
import error while performing ptestlong

sage 8.1.rc3 (also appears in earlier versions) "make ptestlong":

sage is accessing old installation of sympy, which is located in the last path of PYTHONPATH

~$ echo $PYTHONPATH
:/home/georg/data/sync/software/Python:/tmp/pytex:/home/georg/data/sync/.system/extensions/python/lib:/home/georg/data/sync/.system/extensions/python/external_modules

I know I have to clean up my environment!
Unsetting PYTHONPATH solves this issue and ptestlong runs without any fail.
But shouldn't use sage it's own version of sympy before tracing back to another one?

Doctesting 3630 files using 8 threads.
Traceback (most recent call last):
  File "/mnt/software/sage-8.1.rc3/src/bin/sage-runtests", line 125, in <module>
    err = DC.run()
  File "/mnt/software/sage-8.1.rc3/local/lib/python2.7/site-packages/sage/doctest/control.py", line 1144, in run
    self.run_doctests()
  File "/mnt/software/sage-8.1.rc3/local/lib/python2.7/site-packages/sage/doctest/control.py", line 867, in run_doctests
    self.dispatcher = DocTestDispatcher(self)
  File "/mnt/software/sage-8.1.rc3/local/lib/python2.7/site-packages/sage/doctest/forker.py", line 1403, in __init__
    init_sage()
  File "/mnt/software/sage-8.1.rc3/local/lib/python2.7/site-packages/sage/doctest/forker.py", line 134, in init_sage
    from sympy.printing.pretty.stringpict import stringPict
  File "/home/georg/data/sync/.system/extensions/python/external_modules/sympy/__init__.py", line 27, in <module>
    raise ImportError("It appears 2to3 has been run on the codebase. Use "
ImportError: It appears 2to3 has been run on the codebase. Use Python 3 or get the original source code.
Makefile:113: recipe for target 'ptestlong' failed
make: *** [ptestlong] Error 1

Georg


Ralf Stephan

unread,
Nov 26, 2017, 10:17:42 AM11/26/17
to sage-release
Datapoint: PYTHONPATH was removed from Sage in 8-0.beta0
See #22608.

Eric Gourgoulhon

unread,
Nov 28, 2017, 7:33:58 AM11/28/17
to sage-release
Hi,
The same Jmol error has just been reported by a Sage user with a different system: Windows 10 and Sage from the Windows installer:
Note that in my case, the error appears only in parallel doctesting (i.e. make ptestlong), while in his case, it is systematic. 

Eric.

Emmanuel Charpentier

unread,
Nov 30, 2017, 3:50:24 PM11/30/17
to sage-release
I jus checked that 8.0.rc3 doesn't build without Trac#24121. If we want to release 8.1 wit Cygwin as an official platform, this is needed...

--
Emmanuel Charpentier


Le vendredi 24 novembre 2017 00:35:13 UTC+1, Volker Braun a écrit :

Sébastien Labbé

unread,
Dec 1, 2017, 1:43:16 AM12/1/17
to sage-release

On Ubuntu 16.04, I get problem building python2-2.7.14.p2 during make ptestlong.

The error is reproducable when I perform sage -i python2

End of log is below

...

gcc -pthread -shared -L. -L/home/slabbe/GitBox/sage/local/lib -Wl,-rpath,/home/slabbe/GitBox/sage/local/lib -L. -L/home/slabbe/GitBox/sage/local/lib -Wl,-rpath,/home/slabbe/GitBox/sage/local/lib build/temp.linux-x86_64-2.7/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Modules/_ctypes/_ctypes.o build/temp.linux-x86_64-2.7/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Modules/_ctypes/callbacks.o build/temp.linux-x86_64-2.7/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Modules/_ctypes/callproc.o build/temp.linux-x86_64-2.7/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Modules/_ctypes/stgdict.o build/temp.linux-x86_64-2.7/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Modules/_ctypes/cfield.o build/temp.linux-x86_64-2.7/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Modules/_ctypes/libffi/src/prep_cif.o build/temp.linux-x86_64-2.7/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Modules/_ctypes/libffi/src/closures.o build/temp.linux-x86_64-2.7/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Modules/_ctypes/libffi/src/x86/ffi64.o build/temp.linux-x86_64-2.7/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Modules/_ctypes/libffi/src/x86/unix64.o build/temp.linux-x86_64-2.7/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Modules/_ctypes/libffi/src/x86/ffi.o build/temp.linux-x86_64-2.7/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Modules/_ctypes/libffi/src/x86/sysv.o -L/home/slabbe/GitBox/sage/local/lib -L/usr/lib/x86_64-linux-gnu -L/usr/local/lib -L. -lpython2.7 -o build/lib.linux-x86_64-2.7/_ctypes.so
*** WARNING: renaming "_ctypes" since importing it failed: build/lib.linux-x86_64-2.7/_ctypes.so: undefined symbol: _PySlice_Unpack

Python build finished, but the necessary bits to build these modules were not found:
bsddb185           dl                 gdbm           
imageop            sunaudiodev                       
To find the necessary bits, look in setup.py in detect_modules() for the module's name.


Failed to build these modules:
_ctypes            _elementtree       _multiprocessing
array              mmap                              

running build_scripts
creating build/scripts-2.7
copying and adjusting /home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Tools/scripts/pydoc -> build/scripts-2.7
copying and adjusting /home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Tools/scripts/idle -> build/scripts-2.7
copying and adjusting /home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Tools/scripts/2to3 -> build/scripts-2.7
copying and adjusting /home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Lib/smtpd.py -> build/scripts-2.7
changing mode of build/scripts-2.7/pydoc from 664 to 775
changing mode of build/scripts-2.7/idle from 664 to 775
changing mode of build/scripts-2.7/2to3 from 664 to 775
changing mode of build/scripts-2.7/smtpd.py from 664 to 775
make[3]: Leaving directory '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src'
Testing importing of various modules...

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2/src/Lib/ctypes/__init__.py", line 7, in <module>
    from _ctypes import Union, Structure, Array
ImportError: No module named _ctypes
ctypes module failed to import
math module imported OK
hashlib module imported OK
crypt module imported OK
readline module imported OK
socket module imported OK
Error: One or more modules failed to import.

real    2m25.869s
user    2m5.516s
sys    0m6.272s
************************************************************************
Error building package python2-2.7.14.p2
************************************************************************
Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /home/slabbe/GitBox/sage/logs/pkgs/python2-2.7.14.p2.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2 and type 'make' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/python2-2.7.14.p2' && '/home/slabbe/GitBox/sage/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.
************************************************************************

Emmanuel Charpentier

unread,
Dec 1, 2017, 12:43:32 PM12/1/17
to sage-release
One more data point : On Cygwin, 8.0.rc3 + Trac#24121 + Trac#21233 + Trac#24297 ( + Trac#24306 + Trac#24240, but the latter two are irrelevant, IMHO) builds and passes ptestlong with no permanent error (I get a transient error while testing src/sage/groups/finitely_presented_named.py, which does not happent when ran standalone).

HTH,

--
Emmanuel Charpentier

Sébastien Labbé

unread,
Dec 1, 2017, 3:32:19 PM12/1/17
to sage-release

ImportError: No module named _ctypes
ctypes module failed to import
math module imported OK
hashlib module imported OK
crypt module imported OK
readline module imported OK
socket module imported OK
Error: One or more modules failed to import.

real    2m25.869s
user    2m5.516s
sys    0m6.272s
************************************************************************
Error building package python2-2.7.14.p2
************************************************************************

The above problem I posted earlier disapeared after make distclean & make.

Sébastien Labbé

unread,
Dec 1, 2017, 3:58:14 PM12/1/17
to sage-release
... and I get "All tests passed!" after make ptestlong. Thank you.

Reply all
Reply to author
Forward
0 new messages