Sage 10.2.rc1 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

I just corrected a mistake, so if your head commit is not e349b002499 then please reset.

e349b002499  (tag: 10.2.rc1, github/develop) Updated SageMath version to 10.2.rc1
81bf4e52c66 gh-36668: CI Linux: Fix "optional", "experimental" jobs
dfde868e2f2 gh-36663: Upgrade `zeromq` to 4.3.5, `pyzmq` to 25.1.1, patch out broken tests in setup
7cad4fc0026 gh-36661: .github/workflows/doc-build.yml: Fix live doc building
781dbff5cb4 gh-36659: prompt_toolkit: Set version constraint for conda
a88fe91eae2 gh-36652: src/sage/misc/sageinspect.py: Fix pycodestyle complaint
9d2750c52bd gh-36648: CI macOS: Update
07ea7e18328 gh-36636: Deploy live doc on push to develop
88984731816 gh-36599: sage-env: identify the version of command-line tools (OS X) and set LDFLAGS accordingly
31a1ae59c46 gh-36534: CI Linux: Fix `centos-7` after #36435, remove `gentoo-python3.12` for now, use `conda-forge` with `-python3.11`
b7d34011471 gh-36533: `pkgs/sage-conf_pypi`: Repair after #36400, #36435
ebef87aa8db (tag: 10.2.rc0) Updated SageMath version to 10.2.rc0

[Dima Pasechnik]

Hi Volker,

could you please merge https://github.com/sagemath/sage/pull/36669 ?
It's just documentation (and promoting work of my student)

Dima

> --
> 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/5e861409-f499-4cd6-8463-9393aca33913n%40googlegroups.com.

[John H Palmieri]

On OS X Intel, looks good. Four doctest failures, all of which have been reported:

sage -t --long --random-seed=120467112235779717922036180522489127126 src/sage/libs/giac/__init__.py  # Timed out
sage -t --long --random-seed=120467112235779717922036180522489127126 src/sage/rings/polynomial/multi_polynomial_ideal.py  # Timed out
sage -t --long --random-seed=120467112235779717922036180522489127126 src/sage/rings/polynomial/polynomial_element.pyx  # 1 doctest failed
sage -t --long --random-seed=120467112235779717922036180522489127126 src/sage/tests/books/computational-mathematics-with-sagemath/mpoly_doctest.py  # 1 doctest failed

(The first two at #35646, the second two at #36509. I have not seen progress fixing either, so there are no associated blocker PRs.)

[John H Palmieri]

Same on OS X Apple M2 chip. In both this and the earlier case, I ran `./configure` — no need to do `./configure --with-system-gfortran=no`.

[John H Palmieri]

A better link for the 3rd and 4th failures is #36631 (https://github.com/sagemath/sage/issues/36631).

On Saturday, November 11, 2023 at 9:52:26 AM UTC-8 John H Palmieri wrote:

[Emmanuel Charpentier]

FWIW, on Debian testing r GB RAM, upgading 10.2.beta9 to 10.2.rc1 and running ptestlong results in one permanent failure :

sage -t --long --warn-long 291.5 --random-seed=166120603893570771975522737524674489931 src/sage/functions/special.py # 2 doctests failed

And, BTW, using view() from a console still fails. I understand that this PR has been positively reviewed ; incorporating it in 10.2 seems useful, to avoid loss of (basic) functionality…

HTH,

​

[David Coudert]

> I just corrected a mistake, so if your head commit is not e349b002499 then please reset.

Can anyone explain me the proper procedure to do that ?
Should I reset head in the branch develop and then force push to the develop branch of my GitHub clone ?

I’m not a git / GitHub expert.

Thanks,
David.

[Volker Braun]

Reset a local branch:

git reset --hard e349b002499

force push to the remote branch of your choice as usual.

[Kenji Iohara]

On Mac OS 13.6.1 with Intel Core i5, I should run ./configure —with-system-gfortran=no to  compile from the first built. 

11/11/2023 20:09、John H Palmieri <jhpalm...@gmail.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.

To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/1dc6aae1-c767-4705-b626-84640fdc9b53n%40googlegroups.com.