Sage 10.6.rc0 released
149 views
Skip to first unread message
Volker Braun
Mar 22, 2025, 11:37:30 AMMar 22
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
d72c36f6bbc gh-39739: minor details in the quivers folder
f619fa8bed0 gh-39738: update msolve to version 7.5
7b99c151454 gh-39732: Update docstring on E2
b9cd9924507 gh-39724: Fixing the cartesian product of a CFM and a generic object.
d37887beb20 gh-39722: ⬆️ Bump tj-actions/changed-files from 45 to 46
7a172213d72 gh-39711: Allow negative shift for flint rational polynomial
4e7e01c11d4 gh-39701: Use uv for linter workflow
df1c72db8c4 gh-39700: Fix typo in SAGE_PARI_MINVER
11faf8a1c19 gh-39699: Fixing the ruff linting
6bacecc7f59 gh-39693: Added the rank method under ModulesWithBasis.ParentMethod.
b1e6aa72aed gh-39686: update sphinxcontrib packages
087ee1fe1ed gh-39685: handling a few unused variables in geometry,graphs,numerical,structure
e09181b6804 gh-39683: spaces around modulo in combinat and rings
280481b8c47 gh-39680: sphinxcontrib-htmlhelp 2.1.0
dab779936aa gh-39678: Optimize MatchingCoveredGraph’s add_edge method
e14b0a2874f gh-39676: update networkx to 3.4.2
cfb586eafb2 gh-39675: update trove_classifiers to 2025.3.3
5f642622dcd gh-39673: en/thematic_tutorials/profiling.rst: update runsnake docs
0d90b5cc8ff gh-39671: fix overflow in Matrix_modn_dense
fec0504c022 gh-39670: CI: Remove broken Linux Mint and openSUSE runs
d9ce3d5032e gh-39665: Added example in digits function to showcase that the sum of digits can be computed
588b400432d gh-39664: Add some 'not tested' marks to avoid CI failure
943b1b4bca0 gh-39655: update numpy to 2.2.3, scipy to 1.15.2
2b78201953c gh-39654: Pybind11, version 2.13.6
3d84fb63697 gh-39653: ninja_build: Update to 1.12.1
bff2e23d168 gh-39652: pythran 0.17.0, switch to wheel
9e362402b3d gh-39645: Remove deprecated PseudoQuaternionicProjectivePlane alias
03c577831e5 gh-39638: fix typo in ladder_idempotent
077c322437b gh-39637: large cleanup in one cluster file
185fd5f63b0 gh-39622: Fix CI documentation diff
0ae7bd58fcf gh-39574: Fixed issue causing the quotient of vector subspaces to throw an exception when divisor is the zero space
9e94658ec60 gh-39444: Improve is_empty and is_finite in a few cases
d15e713834e gh-39296: fix the behavior for immutable graphs in methods related to isomorphisms in `sage/graphs/generic_graph.py`
653eff8da89 gh-39274: Remove `--fiximports` helper
607042ca23d gh-39234: more uses of cached_method in modular folder
8e3c298a321 gh-39221: new implementation of method `is_transitive` with linear memory space
f60d8f7ac1b gh-39069: Mention .coerce() method in coercion tour
8315f4a708e gh-38879: Run meson-ci for MacOS
c62cd675483 gh-38703: Implementation of Ore modules
b9186e06bbe gh-37189: Constructor quaternion algebra over number fields from ramification
7d830638dc9 (tag: 10.6.beta9) Updated SageMath version to 10.6.beta9
Enrique Artal
Mar 24, 2025, 7:41:15 AMMar 24
to sage-release
Built for fedora 41; I have a new problem. I can run jupyterlab inside sage with sage - n jupyterlab, but I cannot use it in the system jupyterlab; I can for 10.5 and I could run it for the previous beta. The logs are strange but it seems related to numpy and matplotlib:
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/bin/sage-venv-config", line 4, in <module>
__import__('pkg_resources').require('sagemath-standard==10.6rc0')
~~~~~~~~~~^^^^^^^^^^^^^^^^^
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 3656, in <module>
@_call_aside
^^^^^^^^^^^
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 3640, in _call_aside
f(*args, **kwargs)
~^^^^^^^^^^^^^^^^^
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 3669, in _initialize_master_working_set
working_set = _declare_state('object', 'working_set', WorkingSet._build_master())
~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 658, in _build_master
return cls._build_from_requirements(__requires__)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 671, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 890, in resolve
dist = self._resolve_dist(
req, best, replace_conflicting, env, installer, required_by, to_activate
)
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 936, in _resolve_dist
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (numpy 2.2.3 (/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib/python3.13/site-packages), Requirement.parse('numpy<2,>=1.21'), {'matplotlib'})
/usr/bin/python3: Error while finding module specification for 'sage.repl.ipython_kernel' (ModuleNotFoundError: No module named 'sage')
Traceback (most recent call last):
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/bin/sage-venv-config", line 4, in <module>
__import__('pkg_resources').require('sagemath-standard==10.6rc0')
~~~~~~~~~~^^^^^^^^^^^^^^^^^
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 3656, in <module>
@_call_aside
^^^^^^^^^^^
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 3640, in _call_aside
f(*args, **kwargs)
~^^^^^^^^^^^^^^^^^
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 3669, in _initialize_master_working_set
working_set = _declare_state('object', 'working_set', WorkingSet._build_master())
~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 658, in _build_master
return cls._build_from_requirements(__requires__)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 671, in _build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 890, in resolve
dist = self._resolve_dist(
req, best, replace_conflicting, env, installer, required_by, to_activate
)
File "/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib64/python3.13/site-packages/pkg_resources/__init__.py", line 936, in _resolve_dist
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (numpy 2.2.3 (/usr/local/sagedev/local/var/lib/sage/venv-python3.13/lib/python3.13/site-packages), Requirement.parse('numpy<2,>=1.21'), {'matplotlib'})
/usr/bin/python3: Error while finding module specification for 'sage.repl.ipython_kernel' (ModuleNotFoundError: No module named 'sage')
Emmanuel Charpentier
Mar 25, 2025, 6:20:46 AMMar 25
to sage-release
On Debian testing running on Ryzen 9 + 44 GB RAM, upgrading 6.10.beta9 to 6.10.rc0 and running ptestlong :
Problem with recompiling msolve, solved by installing the relevant Debian package and reconfiguring to use it.
Two transient failures (pass when ran standalone) :
- three permanent failures, already reported :
HTH,
Dima Pasechnik
Mar 25, 2025, 10:54:52 AMMar 25
to sage-r...@googlegroups.com
On 25 March 2025 05:20:46 GMT-05:00, Emmanuel Charpentier <emanuel.c...@gmail.com> wrote:
>
>
>On Debian testing running on Ryzen 9 + 44 GB RAM, upgrading 6.10.beta9 to
>6.10.rc0 and running ptestlong :
>
>
> Problem with recompiling msolve, solved by installing the relevant
> Debian package and reconfiguring to use it.
Could you give more details about msolve problem you saw?
> Problem with recompiling msolve, solved by installing the relevant
> Debian package and reconfiguring to use it.
> -
>
> Two transient failures (pass when ran standalone) :
>
>sage -t --long --warn-long 30.0
>--random-seed=283789938022414502874742457010629897766
>src/sage/rings/polynomial/plural.pyx # SignalError in doctesting framework
>sage -t --long --warn-long 30.0
>--random-seed=283789938022414502874742457010629897766
>src/sage/algebras/fusion_rings/fusion_ring.py # Timed out
>
> - three permanent failures, already reported :
> Two transient failures (pass when ran standalone) :
>
>sage -t --long --warn-long 30.0
>--random-seed=283789938022414502874742457010629897766
>src/sage/rings/polynomial/plural.pyx # SignalError in doctesting framework
>sage -t --long --warn-long 30.0
>--random-seed=283789938022414502874742457010629897766
>src/sage/algebras/fusion_rings/fusion_ring.py # Timed out
>
dim...@gmail.com
Mar 25, 2025, 12:46:00 PMMar 25
to sage-r...@googlegroups.com
On Mon, Mar 24, 2025 at 04:41:15AM -0700, Enrique Artal wrote:
> Built for fedora 41; I have a new problem. I can run jupyterlab inside sage
> with sage - n jupyterlab, but I cannot use it in the system jupyterlab; I
> can for 10.5 and I could run it for the previous beta. The logs are strange
> but it seems related to numpy and matplotlib:
Yes, it seems that our old version of matplotlib needs a bump (one way or
> Built for fedora 41; I have a new problem. I can run jupyterlab inside sage
> with sage - n jupyterlab, but I cannot use it in the system jupyterlab; I
> can for 10.5 and I could run it for the previous beta. The logs are strange
> but it seems related to numpy and matplotlib:
another).
I'll do a PR for this now.
Does the error go away if you pip-install the latest matplotlib via
./sage --pip ?
> 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 visit https://groups.google.com/d/msgid/sage-release/ec7420c0-220e-484a-9620-b187e12562d0n%40googlegroups.com.
dim...@gmail.com
Mar 25, 2025, 1:54:01 PMMar 25
to sage-r...@googlegroups.com
On Mon, Mar 24, 2025 at 04:41:15AM -0700, Enrique Artal wrote:
> Built for fedora 41; I have a new problem. I can run jupyterlab inside sage
> with sage - n jupyterlab, but I cannot use it in the system jupyterlab; I
> can for 10.5 and I could run it for the previous beta. The logs are strange
> but it seems related to numpy and matplotlib:
Please see https://github.com/sagemath/sage/pull/39789
> with sage - n jupyterlab, but I cannot use it in the system jupyterlab; I
> can for 10.5 and I could run it for the previous beta. The logs are strange
> but it seems related to numpy and matplotlib:
for a fix
Emmanuel Charpentier
Mar 27, 2025, 8:24:55 AMMar 27
to sage-release
Le mardi 25 mars 2025 à 15:54:52 UTC+1, Dima Pasechnik a écrit :
On 25 March 2025 05:20:46 GMT-05:00, Emmanuel Charpentier <emanuel.c...@gmail.com> wrote:
>
>
>On Debian testing running on Ryzen 9 + 44 GB RAM, upgrading 6.10.beta9 to
>6.10.rc0 and running ptestlong :
>
> -
>
> Problem with recompiling msolve, solved by installing the relevant
> Debian package and reconfiguring to use it.
Could you give more details about msolve problem you saw?
Sorry : I didn’t think of saving the relevant log before installing the system’s msolve, and routinely rmed it in order to avoid a false alarm when recompiling. Silly me…
Sorry also for the delay in answering : I have currently severe connectivity problems (ADSL line down for a while, connexion via phone of questionable reliability…).
Reply all
Reply to author
Forward
0 new messages