Sage 9.8.beta7 released

224 views
Skip to first unread message

Volker Braun

unread,
Jan 18, 2023, 6:48:25 PM1/18/23
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

We should probably gear up for a 9.8 release soon, so get your tickets ready ;)

047281e0287 (trac/develop, tag: 9.8.beta7) Updated SageMath version to 9.8.beta7
272c557d1f3 Trac #31668: Run TestSuite on polynomial rings
6f8fb9ba3ef Trac #22067: generating function of integral points of polyhedra
5544a33b815 Trac #21003: Add package pyscipopt, add MIP backend
b0422b2536b Trac #34838: setuptools_scm, contourpy, sphinxcontrib_websupport, typing_extensions: Add missing dependencies
30d58156a46 Trac #34717: Check the presence of lrsnash for obtain_nash()
c7299453922 Trac #34891: fixing some E502 in tensor, dynamics, modules, plot, numerical
bc832cb3578 Trac #34889: Installation guide: On WSL, clear /mnt/c stuff from PATH
3570a9a63bd Trac #34881: allow to remove no constraints
0ceb1032430 Trac #34878: MixedIntegerLinearProgram.add_constraint: Option to return row indices, fix handling of empty constraints
df74efb66d2 Trac #34859: sagelib: Remove unnecessary import of typing_extensions
b6a76d7a848 Trac #34857: bump giac's GIAC_MIN_VERSION to 1.9
6a8155e6e5d Trac #34854: molien_series() should not use GAP's VirtualCharacter
dddf3ca0b08 Trac #34853: sage-env: Fix misconfiguration of pip
6f631021ac4 Trac #34847: modernize some for loops in cython files
9ffabc7f3e1 Trac #34844: removal of some unused imports about string conversion
4b50bc2af27 Trac #34843: pep8 cleanup in ore_polynomial_element.pyx
bdd14cec19b Trac #34837: fix E502 in some pyx files
172ad73ae38 Trac #34836: fix E271 and E272 in rings/ and schemes/
3d861266040 Trac #34749: Packages dsdp, scip_sdp
64d232b5bfd Trac #31329: Update scipoptsuite to 8.0.2 (now open source!), rename to scip
2dcafb3ac57 Trac #34839: Support tox 4
ad68f15d97f Trac #34648: Developer's guide: warn the transition to GitHub and add links to the transition guide
acebbc1a9e8 Trac #34824: do not include parent in hash of parking functions
9a7b6310dde Trac #34818: Error when defining differentials over GCA's with relations.
bb63c582122 Trac #34807: Add Construction of Hadamard matrices up to order 664
8a0b16d93be Trac #34804: Deprecate sage.interfaces is_...Element functions
80f8f950e95 Trac #34793: clean 3 files inside modular
b0cc282500e Trac #34547: Interfaces: use more lazy imports, restore top-level functions maxima_console etc.
5905da7ebfc Trac #33915: inseparable elliptic-curve isogenies
98b22ebdcf7 Trac #32826: scalar-multiplication endomorphisms of elliptic curves
4f11a750df9 Trac #8744: Improve add_edge in BipartiteGraph to make it independent from the current coloring
08aa2f8edaa Trac #33842: Upgrade python to 3.11
75bedf95960 Trac #34783: various details in combinat/
33fa8715bd5 Trac #34742: Optional package soplex (dependency of scip)
f84915f69d8 Trac #34726: Optional package papilo (dependency of scip)
e5cf1c0d9f2 Trac #34694: Bug in ExteriorAlgebra interior product
ebb9b611d02 Trac #34416: Manage pexpect logs created during doctesting
962177a2da1 Trac #33907: interfaces/expect.py random test failure
66409243991 Trac #16522: lazy_import doesn't resolve properly when indirectly imported
2114066f877 (tag: 9.8.beta6) Updated SageMath version to 9.8.beta6

Enrique Artal

unread,
Jan 19, 2023, 4:43:51 AM1/19/23
to sage-release
In Fedora 37 I needed to `make distclean` and use the sage package for python3 and not the system one. The optional package snappy does not compile. Anyway, thanks for the new version. Best, Enrique. 

Dima Pasechnik

unread,
Jan 19, 2023, 6:04:24 AM1/19/23
to sage-r...@googlegroups.com
What's wrong with Fedora's 37 Python3? (3.11.0, right?)
What error do you see in config.log - which tells, hopefully, why it
does not want system's python3 ?
> --
> 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/02b48e4a-95c4-4a17-adb1-b8140e83053dn%40googlegroups.com.

Enrique Artal

unread,
Jan 19, 2023, 7:01:18 AM1/19/23
to sage-release
I tried in another computer with the system package (3.11.1) and it worked but in both cases only after make distclean.
I lost the logs but sagelib complained about setup.
Snappy fails in both cases.

axio...@yahoo.de

unread,
Jan 20, 2023, 6:26:30 AM1/20/23
to sage-release
All of a sudden, emacs sage-shell-mode seems not to work any more?  The last message I get is

Checking IPython version... Done. To disable this checking, set ‘sage-shell:check-ipython-version-on-startup’ to ‘nil’.
error in process filter: Quit [2 times]

The last beta worked.

Anyone else experiencing this?

Martin

axio...@yahoo.de

unread,
Jan 20, 2023, 6:30:23 AM1/20/23
to sage-release
Here is the backtrace:

Debugger entered--Lisp error: (quit)
  accept-process-output(nil 0 1)
  sage-shell:wait-for-redirection-to-complete()
  sage-shell:run-cell-raw-output("_emacs_sage_shell.print_sage_root()" :sync t :process-buffer nil :output-buffer nil :to-string t :raw nil)
  sage-shell:send-command-sync("_emacs_sage_shell.print_sage_root()" nil nil t nil)
  sage-shell:send-command-to-string("_emacs_sage_shell.print_sage_root()")
  sage-shell:after-init-function(#<buffer *Sage*>)
  #f(compiled-function () #<bytecode 0x15933221e03d>)()
  sage-shell:run-hook-once(sage-shell:output-filter-finished-hook)
  sage-shell:output-filter(#<process Sage> "┌─────────────────────────────────────────────────...")
  read-event(nil t 2)
  sit-for(2)
  execute-extended-command(nil "run-sage" "run-sa")
  funcall-interactively(execute-extended-command nil "run-sage" "run-sa")
  call-interactively(execute-extended-command nil nil)
  command-execute(execute-extended-command)

David Coudert

unread,
Jan 20, 2023, 9:52:49 AM1/20/23
to sage-r...@googlegroups.com
Hello,

I'm unable to compile on MacBook Pro M1 with macOS 12.6.1, updated homebrew, after distclean, using a fresh shell, and running ./bootstrap, source .homebrew-build-env, ./configure --enable-download-from-upstream-url, and make build.

Help is more than welcome. I don’t know how to fix that.

I have attached the install.log file (zipped).

The last lines are:
======
[sagelib-9.8.beta7]     sage/tests/stl_vector.cpp:5426:13: warning: unused variable '__pyx_doc_4sage_9structure_7richcmp_8revop' [-Wunused-variable]
[sagelib-9.8.beta7]     static char __pyx_doc_4sage_9structure_7richcmp_8revop[] = "revop(int op) -> int\nFile: sage/structure/richcmp.pxd (starting at line 199)\n\n    Return the reverse operation of ``op``.\n\n    For example, <= becomes >=, etc.\n\n    EXAMPLES::\n\n        sage: from sage.structure.richcmp import revop\n        sage: [revop(i) for i in range(6)]\n        [4, 5, 2, 3, 0, 1]\n    ";
[sagelib-9.8.beta7]                 ^
[sagelib-9.8.beta7]     sage/tests/stl_vector.cpp:5707:18: warning: unused function '__pyx_pw_4sage_7cpython_6string_1bytes_to_str' [-Wunused-function]
[sagelib-9.8.beta7]     static PyObject *__pyx_pw_4sage_7cpython_6string_1bytes_to_str(PyObject *__pyx_self, PyObject *__pyx_args, PyObject *__pyx_kwds) {
[sagelib-9.8.beta7]                      ^
[sagelib-9.8.beta7]     sage/tests/stl_vector.cpp:5706:13: warning: unused variable '__pyx_doc_4sage_7cpython_6string_bytes_to_str' [-Wunused-variable]
[sagelib-9.8.beta7]     static char __pyx_doc_4sage_7cpython_6string_bytes_to_str[] = "bytes_to_str(b, encoding=None, errors=None) -> unicode\nFile: sage/cpython/string.pxd (starting at line 28)\n\n    Convert ``bytes`` to ``str``.\n\n    This decodes the given ``bytes`` to a Python 3 unicode ``str`` using\n    the specified encoding.  It is a no-op on ``str`` input.\n\n    EXAMPLES::\n\n        sage: from sage.cpython.string import bytes_to_str\n        sage: s = bytes_to_str(b'\\xcf\\x80')\n        sage: s == u'\317\200'\n        True\n        sage: bytes_to_str([])\n        Traceback (most recent call last):\n        ...\n        TypeError: expected bytes, list found\n    ";
[sagelib-9.8.beta7]                 ^
[sagelib-9.8.beta7]     sage/tests/stl_vector.cpp:5912:18: warning: unused function '__pyx_pw_4sage_7cpython_6string_3str_to_bytes' [-Wunused-function]
[sagelib-9.8.beta7]     static PyObject *__pyx_pw_4sage_7cpython_6string_3str_to_bytes(PyObject *__pyx_self, PyObject *__pyx_args, PyObject *__pyx_kwds) {
[sagelib-9.8.beta7]                      ^
[sagelib-9.8.beta7]     sage/tests/stl_vector.cpp:5911:13: warning: unused variable '__pyx_doc_4sage_7cpython_6string_2str_to_bytes' [-Wunused-variable]
[sagelib-9.8.beta7]     static char __pyx_doc_4sage_7cpython_6string_2str_to_bytes[] = "str_to_bytes(s, encoding=None, errors=None) -> bytes\nFile: sage/cpython/string.pxd (starting at line 54)\n\n    Convert ``str`` or ``unicode`` to ``bytes``.\n\n    It encodes the given ``str`` to a Python 3 ``bytes``\n    using the specified encoding.  It is a no-op on ``bytes`` input.\n\n    EXAMPLES::\n\n        sage: from sage.cpython.string import str_to_bytes\n        sage: bs = [str_to_bytes(u'\317\200')]\n        sage: all(b == b'\\xcf\\x80' for b in bs)\n        True\n        sage: str_to_bytes([])\n        Traceback (most recent call last):\n        ...\n        TypeError: expected str... list found\n    ";
[sagelib-9.8.beta7]                 ^
[sagelib-9.8.beta7]     19 warnings generated.
[sagelib-9.8.beta7]     INFO: g++ -std=gnu++11 -bundle -undefined dynamic_lookup -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -L/Users/dcoudert/sage/local/lib -Wl,-rpath,/Users/dcoudert/sage/local/lib -L/Users/dcoudert/sage/local/lib -Wl,-rpath,/Users/dcoudert/sage/local/lib -g -O2 build/temp.macosx-12-arm64-cpython-310/sage/tests/stl_vector.o -lgmp -o build/lib.macosx-12-arm64-cpython-310/sage/tests/stl_vector.cpython-310-darwin.so -lpari
[sagelib-9.8.beta7]     ld: warning: -undefined dynamic_lookup may not work with chained fixups
[sagelib-9.8.beta7]     error: Command "gcc -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk -g -O2 -I/opt/homebrew/Cellar/singular/4.3.1p3/include -I/opt/homebrew/Cellar/singular/4.3.1p3/include/singular -I/opt/homebrew/Cellar/singular/4.3.1p3/include -I/opt/homebrew/Cellar/singular/4.3.1p3/include/singular -I/opt/homebrew/Cellar/singular/4.3.1p3/include -Isage/cpython -I/Users/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/cypari2 -Isage/rings/finite_rings -Isage/libs/ntl -I/Users/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/cysignals -I/Users/dcoudert/sage/src -I/Users/dcoudert/sage/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/numpy/core/include -I/opt/homebrew/opt/pyt...@3.10/Frameworks/Python.framework/Versions/3.10/include/python3.10 -I/Users/dcoudert/sage/local/var/lib/sage/venv-python3.10/include -I/opt/homebrew/opt/pyt...@3.10/Frameworks/Python.framework/Versions/3.10/include/python3.10 -c sage/rings/polynomial/multi_polynomial_libsingular.cpp -o build/temp.macosx-12-arm64-cpython-310/sage/rings/polynomial/multi_polynomial_libsingular.o -std=c++11" failed with exit status 1
[sagelib-9.8.beta7]     error: subprocess-exited-with-error
[sagelib-9.8.beta7]     
[sagelib-9.8.beta7]     × python setup.py develop did not run successfully.
[sagelib-9.8.beta7]     │ exit code: 1
[sagelib-9.8.beta7]     ╰─> See above for output.
[sagelib-9.8.beta7]     
[sagelib-9.8.beta7]     note: This error originates from a subprocess, and is likely not a problem with pip.
[sagelib-9.8.beta7]     full command: /Users/dcoudert/sage/local/var/lib/sage/venv-python3.10/bin/python3 -c '
[sagelib-9.8.beta7]     exec(compile('"'"''"'"''"'"'
[sagelib-9.8.beta7]     # This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py
[sagelib-9.8.beta7]     #
[sagelib-9.8.beta7]     # - It imports setuptools before invoking setup.py, to enable projects that directly
[sagelib-9.8.beta7]     #   import from `distutils.core` to work with newer packaging standards.
[sagelib-9.8.beta7]     # - It provides a clear error message when setuptools is not installed.
[sagelib-9.8.beta7]     # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so
[sagelib-9.8.beta7]     #   setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning:
[sagelib-9.8.beta7]     #     manifest_maker: standard file '"'"'-c'"'"' not found".
[sagelib-9.8.beta7]     # - It generates a shim setup.py, for handling setup.cfg-only projects.
[sagelib-9.8.beta7]     import os, sys, tokenize
[sagelib-9.8.beta7]     
[sagelib-9.8.beta7]     try:
[sagelib-9.8.beta7]         import setuptools
[sagelib-9.8.beta7]     except ImportError as error:
[sagelib-9.8.beta7]         print(
[sagelib-9.8.beta7]             "ERROR: Can not execute `setup.py` since setuptools is not available in "
[sagelib-9.8.beta7]             "the build environment.",
[sagelib-9.8.beta7]             file=sys.stderr,
[sagelib-9.8.beta7]         )
[sagelib-9.8.beta7]         sys.exit(1)
[sagelib-9.8.beta7]     
[sagelib-9.8.beta7]     __file__ = %r
[sagelib-9.8.beta7]     sys.argv[0] = __file__
[sagelib-9.8.beta7]     
[sagelib-9.8.beta7]     if os.path.exists(__file__):
[sagelib-9.8.beta7]         filename = __file__
[sagelib-9.8.beta7]         with tokenize.open(__file__) as f:
[sagelib-9.8.beta7]             setup_py_code = f.read()
[sagelib-9.8.beta7]     else:
[sagelib-9.8.beta7]         filename = "<auto-generated setuptools caller>"
[sagelib-9.8.beta7]         setup_py_code = "from setuptools import setup; setup()"
[sagelib-9.8.beta7]     
[sagelib-9.8.beta7]     exec(compile(setup_py_code, filename, "exec"))
[sagelib-9.8.beta7]     '"'"''"'"''"'"' % ('"'"'/Users/dcoudert/sage/src/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' --no-user-cfg develop --no-deps
[sagelib-9.8.beta7]     cwd: /Users/dcoudert/sage/src/
[sagelib-9.8.beta7] error: subprocess-exited-with-error
[sagelib-9.8.beta7] 
[sagelib-9.8.beta7] × python setup.py develop did not run successfully.
[sagelib-9.8.beta7] │ exit code: 1
[sagelib-9.8.beta7] ╰─> See above for output.
[sagelib-9.8.beta7] 
[sagelib-9.8.beta7] note: This error originates from a subprocess, and is likely not a problem with pip.
[sagelib-9.8.beta7] ********************************************************************************
[sagelib-9.8.beta7] Error installing
[sagelib-9.8.beta7] ********************************************************************************
make[4]: *** [sagelib-SAGE_VENV-no-deps] Error 1
make[3]: *** [/Users/dcoudert/sage/local/var/lib/sage/venv-python3.10/var/lib/sage/installed/sagelib-9.8.beta7] Error 2
make[2]: *** [all-build] Error 2

real 257m24.611s
user 84m34.395s
sys 27m33.538s
***************************************************************
Error building Sage.

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

* package:         sagelib-9.8.beta7
  last build time: 7470835 20 jan
  log file:        /Users/dcoudert/sage/logs/pkgs/sagelib-9.8.beta7.log

It is safe to delete any log files and build directories, but they
contain information that is helpful for debugging build problems.
WARNING: If you now run 'make' again, the build directory of the
same version of the package will, by default, be deleted. Set the
environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.

make[1]: *** [all-build] Error 1
make: *** [build] Error 2
======



install.log.zip

David Coudert

unread,
Jan 20, 2023, 10:04:12 AM1/20/23
to sage-r...@googlegroups.com
And here is file sagely-9.8.beta7.log (zipped)
Best,
David.

sagelib-9.8.beta7.log.zip

Dima Pasechnik

unread,
Jan 20, 2023, 10:20:12 AM1/20/23
to sage-release
is XCode up to date?

--
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.
<install.log.zip>


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

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

David Coudert

unread,
Jan 20, 2023, 10:24:52 AM1/20/23
to sage-r...@googlegroups.com

axio...@yahoo.de

unread,
Jan 20, 2023, 10:50:00 AM1/20/23
to sage-release
I'm sorry, recompiling sage fixed the emacs problem.  I have no idea what happened.

John H Palmieri

unread,
Jan 20, 2023, 12:41:56 PM1/20/23
to sage-release
If you have installed Singular via homebrew, it may be too new for Sage to handle properly. Try "./configure --with-system-singular=no". (I think this would be fixed by https://trac.sagemath.org/ticket/34851.)

--
John

David Coudert

unread,
Jan 20, 2023, 1:44:39 PM1/20/23
to sage-r...@googlegroups.com
Indeed, it’s working well with --with-system-singular=no.
Thank you,
David.

Emmanuel Charpentier

unread,
Jan 20, 2023, 3:26:38 PM1/20/23
to sage-release
I've got the same (extremely annoying) problem. I've opened an issue on  sage-shell-mode Github page.

Emmanuel Charpentier

unread,
Jan 20, 2023, 3:30:02 PM1/20/23
to sage-release
What exactly did you do to "recompile sage" ?

Dima Pasechnik

unread,
Jan 20, 2023, 3:33:23 PM1/20/23
to sage-release
as the package/build system is being updated, it's hard to escape `make distclean`

Perhaps `make sagelib-clean sagelib-uninstall` will do in this case - but perhaps it's some other python module guilty here.


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

Emmanuel Charpentier

unread,
Jan 20, 2023, 3:34:21 PM1/20/23
to sage-release
Apart from the  Emacs issye alteady reported, I get the three permanent failures I reported for the previous betas, as well as a new one, which gives three errors :

charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long --warn-long 259.6 --random-seed=41414648133166628206443904124754495105 src/sage/interfaces/fricas.py  # 3 doctests failed
Running doctests with ID 2023-01-20-20-50-00-ee865d6d.
Git branch: develop
Git ref: 9.8.beta7
Running with SAGE_LOCAL='/usr/local/sage-9/local' and SAGE_VENV='/usr/local/sage-9/local/var/lib/sage/venv-python3.10'
Using --optional=debian,dot2tex,fricas,gap_packages,libsemigroups,mathics,mathics_scanner,msolve,palettable,pint,pip,saclib,sage,sage_spkg
Features to be detected: 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,cvxopt,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
Doctesting 1 file.
sage -t --long --warn-long 259.6 --random-seed=41414648133166628206443904124754495105 src/sage/interfaces/fricas.py
**********************************************************************
File "src/sage/interfaces/fricas.py", line 894, in sage.interfaces.fricas.FriCAS.__reduce__
Failed example:
    fricas.__reduce__()                                           # optional - fricas
Exception raised:

    Traceback (most recent call last):
      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 1093, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.interfaces.fricas.FriCAS.__reduce__[0]>", line 1, in <module>
        fricas.__reduce__()                                           # optional - fricas
      File "/usr/lib/python3.10/copyreg.py", line 76, in _reduce_ex
        raise TypeError(f"cannot pickle {cls.__name__!r} object")
    TypeError: cannot pickle 'LazyImport' object
**********************************************************************
File "src/sage/interfaces/fricas.py", line 896, in sage.interfaces.fricas.FriCAS.__reduce__
Failed example:
    f, args = _                                                   # optional - fricas
Exception raised:

    Traceback (most recent call last):
      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 1093, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.interfaces.fricas.FriCAS.__reduce__[1]>", line 1, in <module>
        f, args = _                                                   # optional - fricas
    TypeError: cannot unpack non-iterable int object
**********************************************************************
File "src/sage/interfaces/fricas.py", line 897, in sage.interfaces.fricas.FriCAS.__reduce__
Failed example:
    f(*args)                                                      # optional - fricas
Exception raised:

    Traceback (most recent call last):
      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 1093, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.interfaces.fricas.FriCAS.__reduce__[2]>", line 1, in <module>
        f(*args)                                                      # optional - fricas
    NameError: name 'f' is not defined
**********************************************************************
1 item had failures:
   3 of   4 in sage.interfaces.fricas.FriCAS.__reduce__
    [277 tests, 3 failures, 42.89 s]
----------------------------------------------------------------------
sage -t --long --warn-long 259.6 --random-seed=41414648133166628206443904124754495105 src/sage/interfaces/fricas.py  # 3 doctests failed
----------------------------------------------------------------------
Total time for all tests: 48.0 seconds
    cpu time: 4.2 seconds
    cumulative wall time: 42.9 seconds
Features detected for doctesting:


HTH,

John H Palmieri

unread,
Jan 20, 2023, 4:46:02 PM1/20/23
to sage-release
Does this change fix the fricas.py failure?

diff --git a/src/sage/interfaces/fricas.py b/src/sage/interfaces/fricas.py
index dc2ce71f26..ceba6f90dc 100644
--- a/src/sage/interfaces/fricas.py
+++ b/src/sage/interfaces/fricas.py
@@ -891,7 +891,7 @@ http://fricas.sourceforge.net.
         """
         EXAMPLES::
 
-            sage: fricas.__reduce__()                                           # optional - fricas
+            sage: FriCAS().__reduce__()                                         # optional - fricas
             (<function reduce_load_fricas at 0x...>, ())
             sage: f, args = _                                                   # optional - fricas
             sage: f(*args)

John H Palmieri

unread,
Jan 20, 2023, 4:58:53 PM1/20/23
to sage-release
In the hopes that this will fix it, I opened https://trac.sagemath.org/ticket/34927.

Emmanuel Charpentier

unread,
Jan 20, 2023, 6:50:35 PM1/20/23
to sage-release
How did you get a backtrace ? I don't get one, just messages in the `*Messages* buffer...

Le vendredi 20 janvier 2023 à 12:30:23 UTC+1, axio...@yahoo.de a écrit :

axio...@yahoo.de

unread,
Jan 21, 2023, 4:10:38 AM1/21/23
to sage-release
M-x toggle-debug-on-quit

(and then hit C-g often enough)

I have two directories with git clones of sage.  When I discovered the problem, I went back to 9.8.beta5 in the first, and then made 9.8.beta7 in the other.  I then tried sage-shell-mode in the other, and it worked.  I then made 9.8.beta7 also in the first, and now it works.

Martin

Emmanuel Charpentier

unread,
Jan 22, 2023, 7:57:10 AM1/22/23
to sage-release

I checked that reverting to 9.8.beta6 (by way of make distclean ; ...) solved my Emacs problem. So the question seems to be “What has changed in the interface used by emacs ?”.

Emmanuel Charpentier

unread,
Jan 22, 2023, 8:41:04 AM1/22/23
to sage-release
This patches fix my Fricas issue indeed. But losing the Emacs interface is a big hit for me, so I revert to 9.6.beta6 for now.

Thank you nevertheless !

tsc...@ucdavis.edu

unread,
Jan 23, 2023, 3:07:32 AM1/23/23
to sage-release
I am getting stuck at giac, even after a make distclean (I rebuilt 9.8.beta6 just to confirm this is a problem with the upgrade and almost certainly due to #34857). Sorry for posting the log files; I can't seem to include attachments...

[giac-1.9.0.15p0] /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: undefined reference to `graph_free@CLIQUER_1'
[giac-1.9.0.15p0] /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: undefined reference to `clique_unweighted_find_single@CLIQUER_1'
[giac-1.9.0.15p0] /usr/bin/ld: /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: undefined reference to `graph_new@CLIQUER_1'
[giac-1.9.0.15p0] collect2: error: ld returned 1 exit status
[giac-1.9.0.15p0] make[7]: *** [Makefile:784: aide] Error 1
[giac-1.9.0.15p0] make[7]: *** Waiting for unfinished jobs....
[giac-1.9.0.15p0] icas.o: in function `texmacs_graph_output(giac::gen const&, giac::gen&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, int, giac::context const*)':
[giac-1.9.0.15p0] /home/travis/sage-build/local/var/tmp/sage/build/giac-1.9.0.15p0/src/src/icas.cc:500: warning: the use of `tmpnam' is dangerous, better use `mkstemp'
[giac-1.9.0.15p0] /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: undefined reference to `graph_free@CLIQUER_1'
[giac-1.9.0.15p0] /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: undefined reference to `clique_unweighted_find_single@CLIQUER_1'
[giac-1.9.0.15p0] /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libnauty.so: undefined reference to `graph_new@CLIQUER_1'
[giac-1.9.0.15p0] collect2: error: ld returned 1 exit status
[giac-1.9.0.15p0] make[7]: *** [Makefile:792: icas] Error 1
[giac-1.9.0.15p0] make[6]: *** [Makefile:507: all-recursive] Error 1
[giac-1.9.0.15p0] make[5]: *** [Makefile:437: all] Error 2
[giac-1.9.0.15p0] **************************************************************************************************************************************************************************
[giac-1.9.0.15p0] Error building giac-1.9.0.15p0
[giac-1.9.0.15p0] **************************************************************************************************************************************************************************

Let me know what specific log info would be useful.

Best,
Travis

Antonio Rojas

unread,
Jan 23, 2023, 3:28:15 AM1/23/23
to sage-release
El lunes, 23 de enero de 2023 a las 9:07:32 UTC+1, tsc...@ucdavis.edu escribió:
I am getting stuck at giac, even after a make distclean (I rebuilt 9.8.beta6 just to confirm this is a problem with the upgrade and almost certainly due to #34857). Sorry for posting the log files; I can't seem to include attachments...

This is an underlinking issue in your distro's nauty package. Given that upstream nauty doesn't build a shared library, it must be caused by some incomplete distro custom patch. Try disabling system nauty.

axio...@yahoo.de

unread,
Jan 23, 2023, 4:48:48 AM1/23/23
to sage-release
Emacs stopped working for me again!  I don't get it.

This is terrible.

François Bissey

unread,
Jan 23, 2023, 4:51:45 AM1/23/23
to sage-r...@googlegroups.com
It is indeed a known issue with nauty on debian/ubuntu. That's the first
time someone mentioned it in a while but it is definitely broken.
> --
> 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
> <mailto:sage-release...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com <https://groups.google.com/d/msgid/sage-release/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com?utm_medium=email&utm_source=footer>.

Emmanuel Charpentier

unread,
Jan 23, 2023, 1:42:37 PM1/23/23
to sage-release
From someone called mantepse in the sage-shell-mode issue on github :

```
It is really strange: I have a 9.8.beta7 build and a 9.8.beta6 build. Apparently, if I first use the beta6 one for sage-shell-mode, I can then use beta7 in the same emacs session.
```

I don't get it either...

There are two short Python files in the current `sahe-shell-mode` emacs package, which are my prime suspects for an incompatibility with Python 3.11. Now for a strategy for debugging *this*...

Any idea ?

Matthias Köppe

unread,
Jan 23, 2023, 1:57:42 PM1/23/23
to sage-release

John H Palmieri

unread,
Jan 23, 2023, 3:32:10 PM1/23/23
to sage-release
Could it be #34547, #16522, or #33842? I'm just taking guesses based on the newly merged tickets.

tsc...@ucdavis.edu

unread,
Jan 23, 2023, 7:30:05 PM1/23/23
to sage-release
Would it be better to just remove nauty or is there a way to force Sage to build and link with its own copy of nauty?

Thanks,
Travis
Message has been deleted

Matthias Köppe

unread,
Jan 23, 2023, 9:28:48 PM1/23/23
to sage-release
./configure --without-system-nauty 

tsc...@ucdavis.edu

unread,
Jan 23, 2023, 9:53:09 PM1/23/23
to sage-release
Thank you, that worked.

Best,
Travis

axio...@yahoo.de

unread,
Jan 24, 2023, 4:21:11 AM1/24/23
to sage-release
Thank you for this suggestion!  I will try with 9.8.beta6 + #33842.  I hope that all dependencies are in the branch.

Martin

axio...@yahoo.de

unread,
Jan 24, 2023, 5:09:23 AM1/24/23
to sage-release
Indeed, that was a great suggestion: 9.8.beta6 works - and it seems that #16522 was already in 9.8.beta6.  However 9.8.beta6 + #34547 fails.
Not sure where to go from here.  Should I open a ticket on trac?

For me personally, this is a blocker, but I have no idea how many emacs users there are.

Martin

axio...@yahoo.de

unread,
Jan 24, 2023, 8:15:53 AM1/24/23
to sage-release
I just spent some time to debug this, but I failed.  The problem seems to be that sage-shell:wait-for-redirection-to-complete in https://github.com/sagemath/sage-shell-mode/blob/80fbb4ee9ed8507d22214ed7a4ffd135c9e8c7c8/sage-shell-mode.el#L889 does not return.  There is only one python file involved, https://github.com/sagemath/sage-shell-mode/blob/master/emacs_sage_shell.py, but I do not see what #34547 has to do with it.  Something about lazy_import maybe?

I can see that in sage-shell:run-cell-raw-output the command

_emacs_sage_shell.run_cell_and_print_msg_id("_emacs_sage_shell.print_sage_root()", ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747start’, ’emacs_sage_shell_msg_idb3d6f70f24e51147305a3aea036ba747end’)

was sent to the process (using process-send-string), and after that,

        (sage-shell:wait-for-redirection-to-complete)

never returns.  I don't know how to debug the python code, unfortunately.  Most importantly, I don't see what changed - what does #34547 have to do with it?

Martin

Matthias Köppe

unread,
Jan 24, 2023, 11:45:50 AM1/24/23
to sage-release
From looking at that file:

In 9.8.beta7:

sage: isinstance(axiom, sage.interfaces.expect.Expect)
False


John H Palmieri

unread,
Jan 24, 2023, 11:47:29 AM1/24/23
to sage-release
This was one of my guesses because that ticket could have changed global behavior of Sage by changing some imports — most of the tickets made more focused changes. Can you start with 9.8.beta6 and just apply some of the changes from #34547? In particular, do things work if you don't include the changes in all_cmdline.py?

--
John


On Tuesday, January 24, 2023 at 5:15:53 AM UTC-8 axio...@yahoo.de wrote:

axio...@yahoo.de

unread,
Jan 24, 2023, 3:52:29 PM1/24/23
to sage-release
I tried to comment out all the changes in all_cmdline.py, but this didn't help.  The diff of src/sage/interfaces/all.py is a bit unclear to me, I don't see what could be a problem there.

simplye...@gmail.com

unread,
Jan 24, 2023, 4:09:30 PM1/24/23
to sage-r...@googlegroups.com
On my Mac OS13.* with updated homebrew,
and Intel Core i5,
it compiled from the first build and make ptestlong all passed…. 

Kenji 

23/01/2023 21:32、John H Palmieri <jhpalm...@gmail.com>のメール:

Could it be #34547, #16522, or #33842? I'm just taking guesses based on the newly merged tickets.
--
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/e29d1d43-f40b-4189-a096-3e036efb32a2n%40googlegroups.com.

John H Palmieri

unread,
Jan 24, 2023, 5:15:40 PM1/24/23
to sage-release
For reasons I really don't understand, removing these lines from sage.interfaces.all seem to have caused this:

-interfaces = ['gap', 'gap3', 'giac', 'gp', 'mathematica', 'gnuplot', \
-              'kash', 'magma', 'macaulay2', 'maple', 'maxima', \
-              'mathematica', 'mwrank', 'octave', 'r', \
-              'singular', 'sage0', 'sage']

At least if I restore those lines, or even just add a line "interfaces = []", then emacs appears to work again. I haven't tried it very much, though.

I have absolutely no idea why this change would make a difference...

Dima Pasechnik

unread,
Jan 24, 2023, 5:30:26 PM1/24/23
to sage-r...@googlegroups.com
On Tue, Jan 24, 2023 at 10:15 PM John H Palmieri <jhpalm...@gmail.com> wrote:
>
> For reasons I really don't understand, removing these lines from sage.interfaces.all seem to have caused this:
>
> -interfaces = ['gap', 'gap3', 'giac', 'gp', 'mathematica', 'gnuplot', \
> - 'kash', 'magma', 'macaulay2', 'maple', 'maxima', \
> - 'mathematica', 'mwrank', 'octave', 'r', \
> - 'singular', 'sage0', 'sage']
>
> At least if I restore those lines, or even just add a line "interfaces = []", then emacs appears to work again. I haven't tried it very much, though.

perhaps cause it's used in emacs_sage_shell.py ?
> --
> 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/1e6d6444-d47f-4eb1-b790-5159fc2c577en%40googlegroups.com.

Emmanuel Charpentier

unread,
Jan 24, 2023, 5:31:38 PM1/24/23
to sage-release

I have absolutely no idea why this change would make a difference…

The explanation is probably in sahe-shell-mode emacs-lisp code, originally written by someone wose emacs-lisp fu is widely heavier than mine.

sage-shell-mode code, as far as I know, isn’t understood by nobodu, since its original author went to greener pas$tures… A concerted effort to understand and comment it might be worthwile…

John H Palmieri

unread,
Jan 24, 2023, 5:47:15 PM1/24/23
to sage-release
I think Matthias found the answer in the emacs-lisp code (discussion at https://trac.sagemath.org/ticket/34547#comment:56).

John H Palmieri

unread,
Jan 24, 2023, 6:12:42 PM1/24/23
to sage-release

Emmanuel Charpentier

unread,
Jan 25, 2023, 7:53:09 AM1/25/23
to sage-release
FWIW, 9.8.beta7 + Trac#34935 runs under `sage-shell-mode`.

Thanks a lot !

Enrique Artal

unread,
Jan 25, 2023, 8:25:38 AM1/25/23
to sage-release
I guess the snappy problem is related to Fedora 37.  A tricky solution is given by upstream team in https://github.com/3-manifolds/SnapPy/issues/88

El jueves, 19 de enero de 2023 a las 13:01:18 UTC+1, Enrique Artal escribió:
I tried in another computer with the system package (3.11.1) and it worked but in both cases only after make distclean.
I lost the logs but sagelib complained about setup.
Snappy fails in both cases.

El jueves, 19 de enero de 2023 a las 12:04:24 UTC+1, Dima Pasechnik escribió:
What's wrong with Fedora's 37 Python3? (3.11.0, right?)
What error do you see in config.log - which tells, hopefully, why it
does not want system's python3 ?

On Thu, Jan 19, 2023 at 9:43 AM Enrique Artal <enriqu...@gmail.com> wrote:
>
> In Fedora 37 I needed to `make distclean` and use the sage package for python3 and not the system one. The optional package snappy does not compile. Anyway, thanks for the new version. Best, Enrique.
> --
> 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.

Dima Pasechnik

unread,
Jan 25, 2023, 9:23:53 AM1/25/23
to sage-r...@googlegroups.com
On Wed, Jan 25, 2023 at 1:25 PM Enrique Artal <enriqu...@gmail.com> wrote:
>
> I guess the snappy problem is related to Fedora 37. A tricky solution is given by upstream team in https://github.com/3-manifolds/SnapPy/issues/88

snappy ships Cython-generated C files. That's the source of trouble...
:facepalm:
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/29f66bc6-3d5f-4537-bd67-3a847d624d03n%40googlegroups.com.

Emmanuel Charpentier

unread,
Jan 25, 2023, 10:22:45 AM1/25/23
to sage-release
After re-building 9.8.beta7 + #34935, running ptestlong gets me one more permanent failure :

```
charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long --warn-long 225.1 --random-seed=121252713509435388240223103279859468631 src/sage/schemes/elliptic_curves/hom_frobenius.py  # 1 doctest failed
Running doctests with ID 2023-01-25-16-07-54-8bb572eb.
Git branch: t/34935/interfaces-emacs
Git ref: 9.8.beta7-1-g49d4ff78cc2

Running with SAGE_LOCAL='/usr/local/sage-9/local' and SAGE_VENV='/usr/local/sage-9/local/var/lib/sage/venv-python3.10'
Using --optional=debian,dot2tex,fricas,gap_jupyter,gap_packages,libsemigroups,mathics,mathics_scanner,msolve,palettable,pari_jupyter,pint,pip,pysingular,sage,sage_spkg,singular_jupyter

Features to be detected: 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,cvxopt,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_cubic_hecke,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.misc.cython,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
Doctesting 1 file.
sage -t --long --warn-long 225.1 --random-seed=121252713509435388240223103279859468631 src/sage/schemes/elliptic_curves/hom_frobenius.py
**********************************************************************
File "src/sage/schemes/elliptic_curves/hom_frobenius.py", line 461, in sage.schemes.elliptic_curves.hom_frobenius.EllipticCurveHom_frobenius.dual
Failed example:
    p in (2,3) or f.dual().dual() == f

Exception raised:
    Traceback (most recent call last):
      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 695, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/usr/local/sage-9/src/sage/doctest/forker.py", line 1093, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.schemes.elliptic_curves.hom_frobenius.EllipticCurveHom_frobenius.dual[17]>", line 1, in <module>
        p in (Integer(2),Integer(3)) or f.dual().dual() == f
      File "sage/misc/cachefunc.pyx", line 2297, in sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__
        self.cache = f(self._instance)
      File "/usr/local/sage-9/src/sage/schemes/elliptic_curves/hom_composite.py", line 689, in dual
        return EllipticCurveHom_composite.from_factors(phis)
      File "/usr/local/sage-9/src/sage/schemes/elliptic_curves/hom_composite.py", line 364, in from_factors
        maps = tuple(maps)
      File "/usr/local/sage-9/src/sage/schemes/elliptic_curves/hom_composite.py", line 688, in <genexpr>
        phis = (phi.dual() for phi in self._phis[::-1])
      File "/usr/local/sage-9/src/sage/schemes/elliptic_curves/ell_curve_isogeny.py", line 3076, in dual
        corr = find_post_isomorphism(mult, rhs)
      File "/usr/local/sage-9/src/sage/schemes/elliptic_curves/hom.py", line 856, in find_post_isomorphism
        isos = [iso for iso in isos if iso._eval(im_phi) == im_psi]
      File "/usr/local/sage-9/src/sage/schemes/elliptic_curves/hom.py", line 856, in <listcomp>
        isos = [iso for iso in isos if iso._eval(im_phi) == im_psi]
      File "/usr/local/sage-9/src/sage/schemes/elliptic_curves/weierstrass_morphism.py", line 586, in _eval
        return self._codomain.base_extend(k).point(Q)
      File "/usr/local/sage-9/src/sage/schemes/elliptic_curves/ell_generic.py", line 1352, in base_extend
        E = constructor.EllipticCurve([R(a) for a in self.a_invariants()])
      File "/usr/local/sage-9/src/sage/schemes/elliptic_curves/ell_generic.py", line 1352, in <listcomp>
        E = constructor.EllipticCurve([R(a) for a in self.a_invariants()])
      File "sage/rings/finite_rings/element_givaro.pyx", line 1355, in sage.rings.finite_rings.element_givaro.FiniteField_givaroElement.__int__
        raise TypeError("Cannot coerce element to an integer.")
    TypeError: Cannot coerce element to an integer.

**********************************************************************
1 item had failures:
   1 of  19 in sage.schemes.elliptic_curves.hom_frobenius.EllipticCurveHom_frobenius.dual
    [117 tests, 1 failure, 0.91 s]
----------------------------------------------------------------------
sage -t --long --warn-long 225.1 --random-seed=121252713509435388240223103279859468631 src/sage/schemes/elliptic_curves/hom_frobenius.py  # 1 doctest failed
----------------------------------------------------------------------
Total time for all tests: 1.0 seconds
    cpu time: 0.9 seconds
    cumulative wall time: 0.9 seconds
Features detected for doctesting:
pytest is not installed in the venv, skip checking tests that rely on it
```

HTH,

Dima Pasechnik

unread,
Jan 25, 2023, 10:51:10 AM1/25/23
to sage-r...@googlegroups.com
Is it givaro from the system?
If so, can you try if building Sage's givaro helps?
> --
> 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/6827802b-b306-4fc9-a1b9-87fe7190ef78n%40googlegroups.com.

Emmanuel Charpentier

unread,
Jan 25, 2023, 12:51:48 PM1/25/23
to sage-release
```
charpent@zen-book-flip:/usr/local/sage-9$ sage -standard | grep givaro
givaro..................................4.1.1 (4.1.1)
```

This means that Sage's givaro is installed,.

I think...

G. M.-S.

unread,
Jan 25, 2023, 2:22:19 PM1/25/23
to sage-r...@googlegroups.com
I also have
sage -standard | grep givaro
givaro..................................4.1.1 (4.1.1)

Reply all
Reply to author
Forward
0 new messages