Sage 10.2.beta7 released

[Volker Braun]

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

b7c1c8fe5cd (tag: 10.2.beta7, github/develop) Updated SageMath version to 10.2.beta7
a84c11dd824 gh-36429: build/pkgs/attrs: Change to wheel package, update dependencies
9bcf11193f3 gh-36426: cleanup of gap3 interface file
0d0447ca11e gh-36424: adding some links for Errors in the doc
45019c3db73 gh-36422: replace wrongly placed sig_on/off pair with sig_check
a216ed31e09 gh-36420: fix for E702 in pyx outside rings
ef7bd8d22a4 gh-36418: .github/workflows/docker.yml: Free more disk space
472121bd914 gh-36415: README: Recommend `configure --config-cache --enable-ccache`
8327845bfae gh-36413: various details in schemes
cfc289b2725 gh-36412: Upgrade `scipy` to 1.11.3, `meson_python` to 0.14.0, `meson` to 1.2.2
6f44770c6d8 gh-36405: `bootstrap-conda`: Refactor, generate versioned environment files
e7165013a9f gh-36403: Fix AttributeError doctests when output includes a suggestion (part of python 3.12 support)
293e4db31a9 gh-36402: bump cysignals to 1.11.4
3bc69cd35f6 gh-36399: fixing category of ncsym and dual
9867e78bbc5 gh-36398: two minor details in groups
2e489923b84 gh-36397: Fix element labeling in `OperationTable.color_table`
41cf2764458 gh-36394: Deprecate the backslash operator
699dbf14c6c gh-36393: `sage --package list`: Sort output, add switches `--{in,ex}clude-dependencies`
384493c12fb gh-36392: a few details in combinat, as suggested by ruff
d0073b27bb3 gh-36391: checking that the system maxima has working help
980a698b0d1 gh-36389: fix for ecl in distros/gentoo.txt
de9da913deb gh-36354: added induced minor function to graph algorithms
6ab9c83be3c gh-36325: Refactor Drinfeld modules subclasses
1943799bff1 gh-36313: tentative of random subset for random matrix
2f1a76dc24a (tag: 10.2.beta6) Updated SageMath version to 10.2.beta6

[Emmanuel Charpentier]

On Debian testing running on core i7 + 16 GB RAM, upgrading 10.2.beta6 to 10.2.beta7 fails with fthe following last lines of test.log :

[ 50626 lines omitted… ]

[sagelib-10.2.beta7] [287/293] Cythonizing sage/rings/real_mpfr.pyx [sagelib-10.2.beta7] multiprocessing.pool.RemoteTraceback: [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] Traceback (most recent call last): [sagelib-10.2.beta7] File "/usr/lib/python3.11/multiprocessing/pool.py", line 125, in worker [sagelib-10.2.beta7] result = (True, func(*args, **kwds)) [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/lib/python3.11/multiprocessing/pool.py", line 48, in mapstar [sagelib-10.2.beta7] return list(map(*args)) [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1325, in cythonize_one_helper [sagelib-10.2.beta7] return cythonize_one(*m) [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1301, in cythonize_one [sagelib-10.2.beta7] raise CompileError(None, pyx_file) [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError: sage/combinat/integer_lists/invlex.pyx [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] [sagelib-10.2.beta7] The above exception was the direct cause of the following exception: [sagelib-10.2.beta7] [sagelib-10.2.beta7] Traceback (most recent call last): [sagelib-10.2.beta7] File "<string>", line 2, in <module> [sagelib-10.2.beta7] File "<pip-setuptools-caller>", line 34, in <module> [sagelib-10.2.beta7] File "/usr/local/sage-10/src/setup.py", line 108, in <module> [sagelib-10.2.beta7] extensions = cythonize( [sagelib-10.2.beta7] ^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1125, in cythonize [sagelib-10.2.beta7] result.get(99999) # seconds [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/lib/python3.11/multiprocessing/pool.py", line 774, in get [sagelib-10.2.beta7] raise self._value [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError: sage/combinat/integer_lists/invlex.pyx [sagelib-10.2.beta7] ************************************************************************ [sagelib-10.2.beta7] Error building the Sage library [sagelib-10.2.beta7] ************************************************************************ [sagelib-10.2.beta7] Please email sage-devel (http://groups.google.com/group/sage-devel) [sagelib-10.2.beta7] explaining the problem and including the relevant part of the log file [sagelib-10.2.beta7] /usr/local/sage-10/logs/pkgs/sagelib-10.2.beta7.log [sagelib-10.2.beta7] Describe your computer, operating system, etc. [sagelib-10.2.beta7] ************************************************************************ [sagelib-10.2.beta7] error: subprocess-exited-with-error [sagelib-10.2.beta7] [sagelib-10.2.beta7] × python setup.py develop did not run successfully. [sagelib-10.2.beta7] │ exit code: 1 [sagelib-10.2.beta7] ╰─> See above for output. [sagelib-10.2.beta7] [sagelib-10.2.beta7] note: This error originates from a subprocess, and is likely not a problem with pip. [sagelib-10.2.beta7] full command: /usr/local/sage-10/local/var/lib/sage/venv-python3.11/bin/python3 -c ' [sagelib-10.2.beta7] exec(compile('"'"''"'"''"'"' [sagelib-10.2.beta7] # This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py [sagelib-10.2.beta7] # [sagelib-10.2.beta7] # - It imports setuptools before invoking setup.py, to enable projects that directly [sagelib-10.2.beta7] # import from `distutils.core` to work with newer packaging standards. [sagelib-10.2.beta7] # - It provides a clear error message when setuptools is not installed. [sagelib-10.2.beta7] # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so [sagelib-10.2.beta7] # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: [sagelib-10.2.beta7] # manifest_maker: standard file '"'"'-c'"'"' not found". [sagelib-10.2.beta7] # - It generates a shim setup.py, for handling setup.cfg-only projects. [sagelib-10.2.beta7] import os, sys, tokenize [sagelib-10.2.beta7] [sagelib-10.2.beta7] try: [sagelib-10.2.beta7] import setuptools [sagelib-10.2.beta7] except ImportError as error: [sagelib-10.2.beta7] print( [sagelib-10.2.beta7] "ERROR: Can not execute `setup.py` since setuptools is not available in " [sagelib-10.2.beta7] "the build environment.", [sagelib-10.2.beta7] file=sys.stderr, [sagelib-10.2.beta7] ) [sagelib-10.2.beta7] sys.exit(1) [sagelib-10.2.beta7] [sagelib-10.2.beta7] __file__ = %r [sagelib-10.2.beta7] sys.argv[0] = __file__ [sagelib-10.2.beta7] [sagelib-10.2.beta7] if os.path.exists(__file__): [sagelib-10.2.beta7] filename = __file__ [sagelib-10.2.beta7] with tokenize.open(__file__) as f: [sagelib-10.2.beta7] setup_py_code = f.read() [sagelib-10.2.beta7] else: [sagelib-10.2.beta7] filename = "<auto-generated setuptools caller>" [sagelib-10.2.beta7] setup_py_code = "from setuptools import setup; setup()" [sagelib-10.2.beta7] [sagelib-10.2.beta7] exec(compile(setup_py_code, filename, "exec")) [sagelib-10.2.beta7] '"'"''"'"''"'"' % ('"'"'/usr/local/sage-10/src/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' --no-user-cfg develop --no-deps [sagelib-10.2.beta7] cwd: /usr/local/sage-10/src/ [sagelib-10.2.beta7] Rolling back uninstall of sagemath-standard [sagelib-10.2.beta7] Moving to /usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/sagemath-standard.egg-link [sagelib-10.2.beta7] from /tmp/pip-uninstall-yh32fysr/sagemath-standard.egg-link [sagelib-10.2.beta7] error: subprocess-exited-with-error [sagelib-10.2.beta7] [sagelib-10.2.beta7] × python setup.py develop did not run successfully. [sagelib-10.2.beta7] │ exit code: 1 [sagelib-10.2.beta7] ╰─> See above for output. [sagelib-10.2.beta7] [sagelib-10.2.beta7] note: This error originates from a subprocess, and is likely not a problem with pip. [sagelib-10.2.beta7] ******************************************************************************** [sagelib-10.2.beta7] Error installing [sagelib-10.2.beta7] ******************************************************************************** [sagelib-10.2.beta7] [sagelib-10.2.beta7] real 2m14,342s [sagelib-10.2.beta7] user 8m4,188s [sagelib-10.2.beta7] sys 0m15,801s make[4]: *** [Makefile:3373 : sagelib-SAGE_VENV-no-deps] Erreur 1 make[3]: *** [Makefile:3373 : /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/installed/sagelib-10.2.beta7] Erreur 2 make[2]: *** [Makefile:2845 : all-start] Erreur 2 make[2] : on quitte le répertoire « /usr/local/sage-10/build/make » real 21m22,612s user 121m45,303s sys 6m8,506s *************************************************************** Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all-start'): * package: sagelib-10.2.beta7 last build time: 16 oct. 08:20 log file: /usr/local/sage-10/logs/pkgs/sagelib-10.2.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.

This is not the first time I see this particular problem, but each time I had tocycle through make distclean, which somehow contradicts the usefulness of make…

I am still unable to understand the problem.

Advice, hints, ideas ?

​

[emanuel.c...@gmail.com]

More examination of the install.log file shows a raft of Cython errors. install.log (compressed) enclosed.

HTH,

[dim...@gmail.com]

On Mon, Oct 16, 2023 at 09:16:46AM +0200, emanuel.c...@gmail.com wrote:
> More examination of the `install.log` file shows a raft of Cython errors. `install.log` (compressed) enclosed.

I think this shows that certain patch for Cython 3.0.2 (Cython PR #5690)
must have been included.
E.g. it's in the branch of https://github.com/sagemath/sage/pull/36332,
the file build/pkgs/cython/patches/5690.patch there

So you can do

git pull <...> pull/36332/head

(where <...> should be the remote name of main Sagemath git repo, often
called origin, or upstream)
to install it, and then run

make cython

followed by

make build



Dima

[Emmanuel Charpentier]

Nope...

`make cython` succeeds. Bit `make build fails :

```
[sagelib-10.2.beta7]     [85/85] Cythonizing sage/symbolic/expression.pyx

[sagelib-10.2.beta7]     multiprocessing.pool.RemoteTraceback:
[sagelib-10.2.beta7]     """
[sagelib-10.2.beta7]     Traceback (most recent call last):
[sagelib-10.2.beta7]       File "/usr/lib/python3.11/multiprocessing/pool.py", line 125, in worker
[sagelib-10.2.beta7]         result = (True, func(*args, **kwds))
[sagelib-10.2.beta7]                         ^^^^^^^^^^^^^^^^^^^
[sagelib-10.2.beta7]       File "/usr/lib/python3.11/multiprocessing/pool.py", line 48, in mapstar
[sagelib-10.2.beta7]         return list(map(*args))
[sagelib-10.2.beta7]                ^^^^^^^^^^^^^^^^
[sagelib-10.2.beta7]       File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1325, in cythonize_one_helper
[sagelib-10.2.beta7]         return cythonize_one(*m)
[sagelib-10.2.beta7]                ^^^^^^^^^^^^^^^^^
[sagelib-10.2.beta7]       File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1301, in cythonize_one
[sagelib-10.2.beta7]         raise CompileError(None, pyx_file)

[sagelib-10.2.beta7]     Cython.Compiler.Errors.CompileError: sage/combinat/combinat_cython.pyx

[sagelib-10.2.beta7]     """
[sagelib-10.2.beta7]
[sagelib-10.2.beta7]     The above exception was the direct cause of the following exception:
[sagelib-10.2.beta7]
[sagelib-10.2.beta7]     Traceback (most recent call last):
[sagelib-10.2.beta7]       File "<string>", line 2, in <module>
[sagelib-10.2.beta7]       File "<pip-setuptools-caller>", line 34, in <module>
[sagelib-10.2.beta7]       File "/usr/local/sage-10/src/setup.py", line 108, in <module>
[sagelib-10.2.beta7]         extensions = cythonize(
[sagelib-10.2.beta7]                      ^^^^^^^^^^
[sagelib-10.2.beta7]       File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1125, in cythonize
[sagelib-10.2.beta7]         result.get(99999)  # seconds
[sagelib-10.2.beta7]         ^^^^^^^^^^^^^^^^^
[sagelib-10.2.beta7]       File "/usr/lib/python3.11/multiprocessing/pool.py", line 774, in get
[sagelib-10.2.beta7]         raise self._value

[sagelib-10.2.beta7]     Cython.Compiler.Errors.CompileError: sage/combinat/combinat_cython.pyx

[sagelib-10.2.beta7]    from /tmp/pip-uninstall-8mtj1z6r/sagemath-standard.egg-link

[sagelib-10.2.beta7] error: subprocess-exited-with-error
[sagelib-10.2.beta7]
[sagelib-10.2.beta7] × python setup.py develop did not run successfully.
[sagelib-10.2.beta7] │ exit code: 1
[sagelib-10.2.beta7] ╰─> See above for output.
[sagelib-10.2.beta7]
[sagelib-10.2.beta7] note: This error originates from a subprocess, and is likely not a problem with pip.
[sagelib-10.2.beta7] ********************************************************************************
[sagelib-10.2.beta7] Error installing
[sagelib-10.2.beta7] ********************************************************************************
[sagelib-10.2.beta7]

[sagelib-10.2.beta7] real 0m51,149s
[sagelib-10.2.beta7] user 2m36,755s
[sagelib-10.2.beta7] sys 0m8,185s

make[4]: *** [Makefile:3373 : sagelib-SAGE_VENV-no-deps] Erreur 1
make[3]: *** [Makefile:3373 : /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/installed/sagelib-10.2.beta7] Erreur 2

make[2]: *** [Makefile:2849 : all-build] Erreur 2

make[2] : on quitte le répertoire « /usr/local/sage-10/build/make »

real 0m51,674s
user 2m39,788s
sys 0m11,577s

***************************************************************
Error building Sage.

The following package(s) may have failed to build (not necessarily

during this run of 'make all-build'):

* package:         sagelib-10.2.beta7
  last build time: 16 oct. 15:01

  log file:        /usr/local/sage-10/logs/pkgs/sagelib-10.2.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]: *** [Makefile:40 : all-build] Erreur 1
make[1] : on quitte le répertoire « /usr/local/sage-10 »
make: *** [Makefile:16 : build] Erreur 2

real 0m52,809s
user 2m41,021s
sys 0m12,733s

```

Hints ?

[Dima Pasechnik]

On Mon, 16 Oct 2023, 14:04 Emmanuel Charpentier, <emanuel.c...@gmail.com> wrote:

Nope...

`make cython` succeeds. Bit `make build fails :

oops, sorry, you need to clean sagelib first.

make sagelib-clean sagelib-uninstall

--
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/26384ee2-c77e-4b3f-a5ba-a228f30972c9n%40googlegroups.com.

[Emmanuel Charpentier]

Nope again : make sagelib-clean sagelib uninstall works, but make -j8 build (or even make build) fails again:

[ Again a bunch of lines elided… ]

[sagelib-10.2.beta7] [553/557] Cythonizing sage/symbolic/expression.pyx [sagelib-10.2.beta7] multiprocessing.pool.RemoteTraceback: [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] Traceback (most recent call last): [sagelib-10.2.beta7] File "/usr/lib/python3.11/multiprocessing/pool.py", line 125, in worker [sagelib-10.2.beta7] result = (True, func(*args, **kwds)) [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/lib/python3.11/multiprocessing/pool.py", line 48, in mapstar [sagelib-10.2.beta7] return list(map(*args)) [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1325, in cythonize_one_helper [sagelib-10.2.beta7] return cythonize_one(*m) [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1301, in cythonize_one [sagelib-10.2.beta7] raise CompileError(None, pyx_file) [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError: sage/algebras/finite_dimensional_algebras/finite_dimensional_algebra_element.pyx [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] [sagelib-10.2.beta7] The above exception was the direct cause of the following exception: [sagelib-10.2.beta7] [sagelib-10.2.beta7] Traceback (most recent call last): [sagelib-10.2.beta7] File "<string>", line 2, in <module> [sagelib-10.2.beta7] File "<pip-setuptools-caller>", line 34, in <module> [sagelib-10.2.beta7] File "/usr/local/sage-10/src/setup.py", line 108, in <module> [sagelib-10.2.beta7] extensions = cythonize( [sagelib-10.2.beta7] ^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1125, in cythonize [sagelib-10.2.beta7] result.get(99999) # seconds [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/lib/python3.11/multiprocessing/pool.py", line 774, in get [sagelib-10.2.beta7] raise self._value [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError: sage/algebras/finite_dimensional_algebras/finite_dimensional_algebra_element.pyx [sagelib-10.2.beta7] ************************************************************************ [sagelib-10.2.beta7] Error building the Sage library [sagelib-10.2.beta7] ************************************************************************ [sagelib-10.2.beta7] Please email sage-devel (http://groups.google.com/group/sage-devel) [sagelib-10.2.beta7] explaining the problem and including the relevant part of the log file [sagelib-10.2.beta7] /usr/local/sage-10/logs/pkgs/sagelib-10.2.beta7.log [sagelib-10.2.beta7] Describe your computer, operating system, etc. [sagelib-10.2.beta7] ************************************************************************ [sagelib-10.2.beta7] error: subprocess-exited-with-error [sagelib-10.2.beta7] [sagelib-10.2.beta7] × python setup.py develop did not run successfully. [sagelib-10.2.beta7] │ exit code: 1 [sagelib-10.2.beta7] ╰─> See above for output. [sagelib-10.2.beta7] [sagelib-10.2.beta7] note: This error originates from a subprocess, and is likely not a problem with pip. [sagelib-10.2.beta7] full command: /usr/local/sage-10/local/var/lib/sage/venv-python3.11/bin/python3 -c ' [sagelib-10.2.beta7] exec(compile('"'"''"'"''"'"' [sagelib-10.2.beta7] # This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py [sagelib-10.2.beta7] # [sagelib-10.2.beta7] # - It imports setuptools before invoking setup.py, to enable projects that directly [sagelib-10.2.beta7] # import from `distutils.core` to work with newer packaging standards. [sagelib-10.2.beta7] # - It provides a clear error message when setuptools is not installed. [sagelib-10.2.beta7] # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so [sagelib-10.2.beta7] # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: [sagelib-10.2.beta7] # manifest_maker: standard file '"'"'-c'"'"' not found". [sagelib-10.2.beta7] # - It generates a shim setup.py, for handling setup.cfg-only projects. [sagelib-10.2.beta7] import os, sys, tokenize [sagelib-10.2.beta7] [sagelib-10.2.beta7] try: [sagelib-10.2.beta7] import setuptools [sagelib-10.2.beta7] except ImportError as error: [sagelib-10.2.beta7] print( [sagelib-10.2.beta7] "ERROR: Can not execute `setup.py` since setuptools is not available in " [sagelib-10.2.beta7] "the build environment.", [sagelib-10.2.beta7] file=sys.stderr, [sagelib-10.2.beta7] ) [sagelib-10.2.beta7] sys.exit(1) [sagelib-10.2.beta7] [sagelib-10.2.beta7] __file__ = %r [sagelib-10.2.beta7] sys.argv[0] = __file__ [sagelib-10.2.beta7] [sagelib-10.2.beta7] if os.path.exists(__file__): [sagelib-10.2.beta7] filename = __file__ [sagelib-10.2.beta7] with tokenize.open(__file__) as f: [sagelib-10.2.beta7] setup_py_code = f.read() [sagelib-10.2.beta7] else: [sagelib-10.2.beta7] filename = "<auto-generated setuptools caller>" [sagelib-10.2.beta7] setup_py_code = "from setuptools import setup; setup()" [sagelib-10.2.beta7] [sagelib-10.2.beta7] exec(compile(setup_py_code, filename, "exec")) [sagelib-10.2.beta7] '"'"''"'"''"'"' % ('"'"'/usr/local/sage-10/src/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' --no-user-cfg develop --no-deps [sagelib-10.2.beta7] cwd: /usr/local/sage-10/src/ [sagelib-10.2.beta7] Rolling back uninstall of sagemath-standard [sagelib-10.2.beta7] Moving to /usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/sagemath-standard.egg-link [sagelib-10.2.beta7] from /tmp/pip-uninstall-k63qels8/sagemath-standard.egg-link [sagelib-10.2.beta7] error: subprocess-exited-with-error [sagelib-10.2.beta7] [sagelib-10.2.beta7] × python setup.py develop did not run successfully. [sagelib-10.2.beta7] │ exit code: 1 [sagelib-10.2.beta7] ╰─> See above for output. [sagelib-10.2.beta7] [sagelib-10.2.beta7] note: This error originates from a subprocess, and is likely not a problem with pip. [sagelib-10.2.beta7] ******************************************************************************** [sagelib-10.2.beta7] Error installing [sagelib-10.2.beta7] ******************************************************************************** [sagelib-10.2.beta7] [sagelib-10.2.beta7] real 2m50,697s [sagelib-10.2.beta7] user 10m53,566s [sagelib-10.2.beta7] sys 0m18,088s make[4]: *** [Makefile:3373 : sagelib-SAGE_VENV-no-deps] Erreur 1 make[3]: *** [Makefile:3373 : /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/installed/sagelib-10.2.beta7] Erreur 2 make[2]: *** [Makefile:2849 : all-build] Erreur 2 make[2] : on quitte le répertoire « /usr/local/sage-10/build/make » real 2m51,203s user 11m5,104s sys 0m31,598s *************************************************************** Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all-build'): * package: sagelib-10.2.beta7 last build time: 16 oct. 16:10 log file: /usr/local/sage-10/logs/pkgs/sagelib-10.2.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]: *** [Makefile:40 : all-build] Erreur 1 make[1] : on quitte le répertoire « /usr/local/sage-10 » make: *** [Makefile:16 : build] Erreur 2 real 2m52,299s user 11m6,822s sys 0m35,210s

​

[Dima Pasechnik]

please post config.log, and logs/pkgs/sagelib-10.2.beta7.log

In your previous install.log I see

[sagelib-10.2.beta7] Error compiling Cython file:
[sagelib-10.2.beta7]
------------------------------------------------------------
[sagelib-10.2.beta7] ...
[sagelib-10.2.beta7] # -*- coding: utf-8 -*-
[sagelib-10.2.beta7] ^
[sagelib-10.2.beta7]
------------------------------------------------------------
[sagelib-10.2.beta7]
[sagelib-10.2.beta7] sage/sets/disjoint_set.pyx:1:0: Compiler
crash in DebugTransform
[sagelib-10.2.beta7]
[sagelib-10.2.beta7]
[sagelib-10.2.beta7] Compiler crash traceback from this point on:
[sagelib-10.2.beta7] File "Cython/Compiler/Visitor.py", line
182, in Cython.Compiler.Visitor.TreeVisitor._visit
[sagelib-10.2.beta7] File
"/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Compiler/ParseTreeTransforms.py",
line 4053, in visit_ModuleNode
[sagelib-10.2.beta7] self.visit_FuncDefNode(nested_funcdef)
[sagelib-10.2.beta7] File
"/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Compiler/ParseTreeTransforms.py",
line 4113, in visit_FuncDefNode
[sagelib-10.2.beta7] self.tb.start(arg.name)
[sagelib-10.2.beta7] File
"/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Debugger/DebugWriter.py",
line 42, in start
[sagelib-10.2.beta7] self.tb.start(name, attrs or {})
[sagelib-10.2.beta7] File "src/lxml/saxparser.pxi", line 841, in
lxml.etree.TreeBuilder.start
[sagelib-10.2.beta7] File "src/lxml/saxparser.pxi", line 769, in
lxml.etree.TreeBuilder._handleSaxStart
[sagelib-10.2.beta7] File "src/lxml/apihelpers.pxi", line 179,
in lxml.etree._makeSubElement
[sagelib-10.2.beta7] File "src/lxml/apihelpers.pxi", line 1754,
in lxml.etree._tagValidOrRaise
[sagelib-10.2.beta7] ValueError: Invalid tag name '.0'

which should disappear from your install.log after you applied the patch.
But the other error, this is something different.

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/6b1c11f9-d21e-46a6-9b81-5ed20099b925n%40googlegroups.com.

[Emmanuel Charpentier]

Would the updated install.log be useful ?

[Dima Pasechnik]

On Mon, Oct 16, 2023 at 4:38 PM Emmanuel Charpentier
<emanuel.c...@gmail.com> wrote:
>
> Would the updated install.log be useful ?

IMHO what we need there is in logs/pkgs/sagelib-10.2.beta7.log

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/6d7c5820-a291-4537-87b9-229a67e1e181n%40googlegroups.com.

[emanuel.c...@gmail.com]

 IMHO what we need there is in logs/pkgs/sagelib-10.2.beta7.log

Here it is.

[Dima Pasechnik]

Please also send config.log, as I already asked.

On Mon, Oct 16, 2023 at 5:27 PM <emanuel.c...@gmail.com> wrote:
>
> IMHO what we need there is in logs/pkgs/sagelib-10.2.beta7.log
>
> Here it is.
>

> --
> 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/3210ca421c3720605652da6ca86165e187c64ccd.camel%40gmail.com.

[Dima Pasechnik]

On Mon, Oct 16, 2023 at 5:29 PM Dima Pasechnik <dim...@gmail.com> wrote:
>
> Please also send config.log, as I already asked.
>
> On Mon, Oct 16, 2023 at 5:27 PM <emanuel.c...@gmail.com> wrote:
> >
> > IMHO what we need there is in logs/pkgs/sagelib-10.2.beta7.log

It looks as if you haven't installed the patch for Cython, as I still see

ValueError: Invalid tag name '.0'

in your log.

You can check this somewhere in the beginning of logs/pkgs/cython*...log
You'd see there "applying patch <such and such>"

[emanuel.c...@gmail.com]

>  Please also send config.log, as I already asked.

Here it is (missed it the first time...).

[Emmanuel Charpentier]

Le lundi 16 octobre 2023 à 18:35:28 UTC+2, Dima Pasechnik a écrit :

On Mon, Oct 16, 2023 at 5:29 PM Dima Pasechnik <dim...@gmail.com> wrote:
>
> Please also send config.log, as I already asked.

Done. See above

>
> On Mon, Oct 16, 2023 at 5:27 PM <emanuel.c...@gmail.com> wrote:
> >
> > IMHO what we need there is in logs/pkgs/sagelib-10.2.beta7.log

It looks as if you haven't installed the patch for Cython, as I still see

ValueError: Invalid tag name '.0'

in your log.

You can check this somewhere in the beginning of logs/pkgs/cython*...log
You'd see there "applying patch <such and such>"

Indeed :

charpent@zen-book-flip:/usr/local/sage-10$ grep patch logs/pkgs/cython-3.0.2.log No patch files found in ../patches

However, I’m pretty certain to have run it (but it has already scrolled off my session transcript) .

I’ll try to start again :

- make sagelib-clean sagelib uninstall - git pull upstream pull/36332/head - make cython - make build

[Emmanuel Charpentier]

Le lundi 16 octobre 2023 à 22:31:38 UTC+2, Emmanuel Charpentier a écrit :

Le lundi 16 octobre 2023 à 18:35:28 UTC+2, Dima Pasechnik a écrit :

On Mon, Oct 16, 2023 at 5:29 PM Dima Pasechnik <dim...@gmail.com> wrote:
>
> Please also send config.log, as I already asked.

Done. See above

>
> On Mon, Oct 16, 2023 at 5:27 PM <emanuel.c...@gmail.com> wrote:
> >
> > IMHO what we need there is in logs/pkgs/sagelib-10.2.beta7.log

It looks as if you haven't installed the patch for Cython, as I still see

ValueError: Invalid tag name '.0'

in your log.

You can check this somewhere in the beginning of logs/pkgs/cython*...log
You'd see there "applying patch <such and such>"

Indeed :

charpent@zen-book-flip:/usr/local/sage-10$ grep patch logs/pkgs/cython-3.0.2.log No patch files found in ../patches

However, I’m pretty certain to have run it (but it has already scrolled off my session transcript) .

I’ll try to start again :

- make sagelib-clean sagelib uninstall - git pull upstream pull/36332/head

BTW :

charpent@zen-book-flip:/usr/local/sage-10$ git pull upstream pull/36332/head Depuis github.com:sagemath/sage * branch refs/pull/36332/head -> FETCH_HEAD Déjà à jour.

(“already up to date”).

[Emmanuel Charpentier]

Then

charpent@zen-book-flip:/usr/local/sage-10$ make cython make build/make/Makefile --stop make[1] : on entre dans le répertoire « /usr/local/sage-10 » make[1]: « build/make/Makefile » est à jour. make[1] : on quitte le répertoire « /usr/local/sage-10 » build/bin/sage-logger \ "cd build/make && ./install 'cython'" logs/install.log make[1] : on entre dans le répertoire « /usr/local/sage-10/build/make » make[1] : on quitte le répertoire « /usr/local/sage-10/build/make » Nothing to (re)build / all up-to-date.

I do not understand. Again…

​

[Dima Pasechnik]

can you check that build/pkgs/cython/patches/5690.patch is there?

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/9bba3b91-09c9-40f0-8945-9d5c7a3c5b24n%40googlegroups.com.

[Emmanuel Charpentier]

Le lundi 16 octobre 2023 à 22:41:38 UTC+2, Dima Pasechnik a écrit :

can you check that build/pkgs/cython/patches/5690.patch is there?

Indeed it is here…

charpent@zen-book-flip:/usr/local/sage-10$ ls build/pkgs/cython/patches/ 5690.patch

And make build still fails :

[sagelib-10.2.beta7] [143/144] Cythonizing sage/symbolic/expression.pyx [sagelib-10.2.beta7] multiprocessing.pool.RemoteTraceback: [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] Traceback (most recent call last): [sagelib-10.2.beta7] File "/usr/lib/python3.11/multiprocessing/pool.py", line 125, in worker [sagelib-10.2.beta7] result = (True, func(*args, **kwds)) [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/lib/python3.11/multiprocessing/pool.py", line 48, in mapstar [sagelib-10.2.beta7] return list(map(*args)) [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1325, in cythonize_one_helper [sagelib-10.2.beta7] return cythonize_one(*m) [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1301, in cythonize_one [sagelib-10.2.beta7] raise CompileError(None, pyx_file) [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError: sage/algebras/finite_dimensional_algebras/finite_dimensional_algebra_element.pyx [sagelib-10.2.beta7] """ [sagelib-10.2.beta7] [sagelib-10.2.beta7] The above exception was the direct cause of the following exception: [sagelib-10.2.beta7] [sagelib-10.2.beta7] Traceback (most recent call last): [sagelib-10.2.beta7] File "<string>", line 2, in <module> [sagelib-10.2.beta7] File "<pip-setuptools-caller>", line 34, in <module> [sagelib-10.2.beta7] File "/usr/local/sage-10/src/setup.py", line 108, in <module> [sagelib-10.2.beta7] extensions = cythonize( [sagelib-10.2.beta7] ^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/Cython/Build/Dependencies.py", line 1125, in cythonize [sagelib-10.2.beta7] result.get(99999) # seconds [sagelib-10.2.beta7] ^^^^^^^^^^^^^^^^^ [sagelib-10.2.beta7] File "/usr/lib/python3.11/multiprocessing/pool.py", line 774, in get [sagelib-10.2.beta7] raise self._value [sagelib-10.2.beta7] Cython.Compiler.Errors.CompileError: sage/algebras/finite_dimensional_algebras/finite_dimensional_algebra_element.pyx [sagelib-10.2.beta7] ************************************************************************ [sagelib-10.2.beta7] Error building the Sage library [sagelib-10.2.beta7] ************************************************************************ [sagelib-10.2.beta7] Please email sage-devel (http://groups.google.com/group/sage-devel) [sagelib-10.2.beta7] explaining the problem and including the relevant part of the log file [sagelib-10.2.beta7] /usr/local/sage-10/logs/pkgs/sagelib-10.2.beta7.log [sagelib-10.2.beta7] Describe your computer, operating system, etc. [sagelib-10.2.beta7] ************************************************************************ [sagelib-10.2.beta7] error: subprocess-exited-with-error [sagelib-10.2.beta7] [sagelib-10.2.beta7] × python setup.py develop did not run successfully. [sagelib-10.2.beta7] │ exit code: 1 [sagelib-10.2.beta7] ╰─> See above for output. [sagelib-10.2.beta7] [sagelib-10.2.beta7] note: This error originates from a subprocess, and is likely not a problem with pip. [sagelib-10.2.beta7] full command: /usr/local/sage-10/local/var/lib/sage/venv-python3.11/bin/python3 -c ' [sagelib-10.2.beta7] exec(compile('"'"''"'"''"'"' [sagelib-10.2.beta7] # This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py [sagelib-10.2.beta7] # [sagelib-10.2.beta7] # - It imports setuptools before invoking setup.py, to enable projects that directly [sagelib-10.2.beta7] # import from `distutils.core` to work with newer packaging standards. [sagelib-10.2.beta7] # - It provides a clear error message when setuptools is not installed. [sagelib-10.2.beta7] # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so [sagelib-10.2.beta7] # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: [sagelib-10.2.beta7] # manifest_maker: standard file '"'"'-c'"'"' not found". [sagelib-10.2.beta7] # - It generates a shim setup.py, for handling setup.cfg-only projects. [sagelib-10.2.beta7] import os, sys, tokenize [sagelib-10.2.beta7] [sagelib-10.2.beta7] try: [sagelib-10.2.beta7] import setuptools [sagelib-10.2.beta7] except ImportError as error: [sagelib-10.2.beta7] print( [sagelib-10.2.beta7] "ERROR: Can not execute `setup.py` since setuptools is not available in " [sagelib-10.2.beta7] "the build environment.", [sagelib-10.2.beta7] file=sys.stderr, [sagelib-10.2.beta7] ) [sagelib-10.2.beta7] sys.exit(1) [sagelib-10.2.beta7] [sagelib-10.2.beta7] __file__ = %r [sagelib-10.2.beta7] sys.argv[0] = __file__ [sagelib-10.2.beta7] [sagelib-10.2.beta7] if os.path.exists(__file__): [sagelib-10.2.beta7] filename = __file__ [sagelib-10.2.beta7] with tokenize.open(__file__) as f: [sagelib-10.2.beta7] setup_py_code = f.read() [sagelib-10.2.beta7] else: [sagelib-10.2.beta7] filename = "<auto-generated setuptools caller>" [sagelib-10.2.beta7] setup_py_code = "from setuptools import setup; setup()" [sagelib-10.2.beta7] [sagelib-10.2.beta7] exec(compile(setup_py_code, filename, "exec")) [sagelib-10.2.beta7] '"'"''"'"''"'"' % ('"'"'/usr/local/sage-10/src/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' --no-user-cfg develop --no-deps [sagelib-10.2.beta7] cwd: /usr/local/sage-10/src/ [sagelib-10.2.beta7] Rolling back uninstall of sagemath-standard [sagelib-10.2.beta7] Moving to /usr/local/sage-10/local/var/lib/sage/venv-python3.11/lib/python3.11/site-packages/sagemath-standard.egg-link [sagelib-10.2.beta7] from /tmp/pip-uninstall-x35mufkn/sagemath-standard.egg-link [sagelib-10.2.beta7] error: subprocess-exited-with-error [sagelib-10.2.beta7] [sagelib-10.2.beta7] × python setup.py develop did not run successfully. [sagelib-10.2.beta7] │ exit code: 1 [sagelib-10.2.beta7] ╰─> See above for output. [sagelib-10.2.beta7] [sagelib-10.2.beta7] note: This error originates from a subprocess, and is likely not a problem with pip. [sagelib-10.2.beta7] ******************************************************************************** [sagelib-10.2.beta7] Error installing [sagelib-10.2.beta7] ******************************************************************************** [sagelib-10.2.beta7] [sagelib-10.2.beta7] real 1m8,293s [sagelib-10.2.beta7] user 3m46,560s [sagelib-10.2.beta7] sys 0m9,187s make[4]: *** [Makefile:3373 : sagelib-SAGE_VENV-no-deps] Erreur 1 make[3]: *** [Makefile:3373 : /usr/local/sage-10/local/var/lib/sage/venv-python3.11/var/lib/sage/installed/sagelib-10.2.beta7] Erreur 2 make[2]: *** [Makefile:2849 : all-build] Erreur 2 make[2] : on quitte le répertoire « /usr/local/sage-10/build/make » real 1m8,804s user 3m51,007s sys 0m14,169s *************************************************************** Error building Sage. The following package(s) may have failed to build (not necessarily during this run of 'make all-build'): * package: sagelib-10.2.beta7 last build time: 16 oct. 22:42 log file: /usr/local/sage-10/logs/pkgs/sagelib-10.2.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]: *** [Makefile:40 : all-build] Erreur 1 make[1] : on quitte le répertoire « /usr/local/sage-10 » make: *** [Makefile:16 : build] Erreur 2 real 1m9,904s user 3m52,308s sys 0m15,791s

[Dima Pasechnik]

for me, the beginning of logs/pkgs/cython-3.0.2.log
on the branch of PR 36332
is as follows. You see, the patch is applied.


Attempting to download package Cython-3.0.2.tar.gz from mirrors
https://www.mirrorservice.org/sites/www.sagemath.org/spkg/upstream/cython/Cython-3.0.2.tar.gz
[......................................................................]
cython-3.0.2
====================================================
Setting up build directory for cython-3.0.2
Finished extraction
Applying patches from ../patches...
Applying ../patches/5690.patch
patching file Cython/Debugger/DebugWriter.py
****************************************************

Why it's not like this for you, I have no idea.

On Mon, Oct 16, 2023 at 9:54 PM Emmanuel Charpentier

> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/ace78125-2f11-4ce6-bf9f-71f88f999057n%40googlegroups.com.

[Dima Pasechnik]

you need

     make cython-clean cython-uninstall

to trigger the rebuild of Cython by 

     make cython

[Emmanuel Charpentier]

```

make sagelib-clean sagelib-uninstall

make cython-clean cython-uninstall

git pull upstream pull/36332/head

make cython

make build

```

seems to have succeded. Tests to be done.

[Emmanuel Charpentier]

On Debian testing running on core i7 + 16 GB RAM, upgrading (awkwardly, see above) 10.2.beta6 to 10.2.beta7 and running ptestlong gives me one transient failure :

sage -t --long --warn-long 214.7 --random-seed=173352811929764019198741857739693451547 src/sage/rings/tests.py # Timed out

and two permanent failures :

sage -t --long --warn-long 214.7 --random-seed=173352811929764019198741857739693451547 src/sage/combinat/posets/posets.py # 1 doctest failed sage -t --long --warn-long 214.7 --random-seed=173352811929764019198741857739693451547 src/sage/functions/special.py # 2 doctests failed

both having been already reported for a few previous betas.

HTH,

​

[David Coudert]

Le 17 oct. 2023 à 12:54, Emmanuel Charpentier <emanuel.c...@gmail.com> a écrit :

On Debian testing running on core i7 + 16 GB RAM, upgrading (awkwardly, see above) 10.2.beta6 to 10.2.beta7 and running ptestlong gives me one transient failure :

sage -t --long --warn-long 214.7 --random-seed=173352811929764019198741857739693451547 src/sage/rings/tests.py # Timed out

and two permanent failures :

sage -t --long --warn-long 214.7 --random-seed=173352811929764019198741857739693451547 src/sage/combinat/posets/posets.py # 1 doctest failed sage -t --long --warn-long 214.7 --random-seed=173352811929764019198741857739693451547 src/sage/functions/special.py # 2 doctests failed

both having been already reported for a few previous betas.

The doctest on posets should be fixed with https://github.com/sagemath/sage/pull/36464

Best,

David.

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/cd6d0eab-7bb0-4065-a460-0fc4acf8f857n%40googlegroups.com.