I propose to remove python3 (and sqlite - which has no other consumers)
from the list of Sage spkgs (packages).
Anno 2025 one has sufficiently many non-Sage ways to make sure a good
enough python3 is available for use with Sage.
We constantly see support cases where users start installing Sage, an
Don't try to build Sage's Python (it's broken on macOS - but some devs
are in denial about it, and refuse to remove this usless, even
harmful, package from Sage).
Use a good, already installed, Python 3.11 or 3.12.
E.g. you can install python3.12 with homebrew:
brew install python@3.12
make su
On Sun, Mar 30, 2025 at 10:39:53AM +0530, 'Vishal Shahi 4-Yr B.Tech.:
Electronics Engg., IIT(BHU)' via sage-devel wrote:
> Even after installing gsl from brew it still shows that gsl will be
> installed as no system package detected what to do ?
it's detected all right, but it depends on openblas
Hi SageMath Community,
I'm Sudarshan Dandgawal, a computer engineering student interested in
contributing to SageMath through Google Summer of Code (GSoC) 2025. I have
been exploring Issue #34504, which addresses inconsistencies in
direct_product, semidirect_product, and direct_product_permgr
