I find it quite difficult to understand the Sage code so I can't
really review the PR. I will say though that I think that this is an
important change to make. Both SymPy and Sage reach deeply into
mpmath's internals which means that mpmath itself is hamstrung when it
comes to future improvements.
https://github.com/sagemath/sage/pull/38113, needs review.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this di
On Sat, Jul 27, 2024 at 10:01 AM 'Martin R' via sage-devel
wrote:
>
> I think it would be good to have a conscious decision about when a merge of
> this pull request should happen. Since it affects 2262 (!) files, just about
> everybody will have to rebase their work. Also, when there is a cle
I'm on a closed network so I cannot provide the log files.
I'm building Sage 10.4 on a RHEL8.10 box using root and GCC 14.1.0. The
configure line was:
./configure --prefix= --enable-build-as-root --enable-wheels
--with-python=
The configure showed lots of packages to be compiled (even though
https://deepmind.google/discover/blog/ai-solves-imo-problems-at-silver-medal-level/
AI achieves silver-medal standard solving International Mathematical
Olympiad problems
Today, we present AlphaProof, a new reinforcement-learning based
system for formal math reasoning, and AlphaGeometry 2, an impr
I think it would be good to have a conscious decision about when a merge of
this pull request should happen. Since it affects 2262 (!) files, just
about everybody will have to rebase their work. Also, when there is a
clear decision, the author will not have to fix merge conflicts again and
ag
