Update Python version requirements to >= 3.12, include Python 3.13 and 3.14 in CI and wheel building, fix CI

[tobiasdiez]

Following https://scientific-python.org/specs/spec-0000/.

Fixes the test CI and wheel building (which are currently broken see eg #34). Also remove a few old/outdated files.

[tobiasdiez]

@dimpase wheel building on macos still fails due to an issue with boost (coming from upstream sage, which is used to install a couple of dependencies):

checking for boostlib >= 1.66.0 (106600)... real_configure: We could not detect the boost libraries (version 1.66.0 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option.  If you are sure you have boost installed, then check your version number looking in <boost/version.hpp>. See http://randspringer.de/boost for more documentation.
  real_configure: error: could not find boost library installation.  https://doc.sagemath.org/html/en/reference/spkg/_prereq.html

It is however installed using homebrew. Any idea how to fix this?

[dimpase]

What " coming from upstream sage" does mean?

EDIT - oops, I see what you mean.

[dimpase]

let me try this locally

[tobiasdiez]

Same issue also on Linux Alpine (boost not found, but installed).

[tobiasdiez]

Is the boost check really necessary in the configure script of sage? If boost is not installed, then meson will just disable the one module that actually relies on it. So I would say it would be fine to just print a warning message, and not exit forcefully with an error.

[dimpase]

I tried building/testing (python3 -m pip install . --user, and testing with pytest) this in Homebrew, with Homebrew Python3.14, with PATH etc set as if we do to build sage-distro (after running source .homebrew-build-env) and it all works.

[dimpase]

Why do you even need upstream Sage here?

[dimpase]

This package does not depend upon Sage, there is absolutely no need to involve Sage in anything related to building its wheel etc. It's just like cysignals and cypari in this sense.

[dimpase]

On November 15, 2025 11:47:22 AM EST, Tobias Diez ***@***.***> wrote: tobiasdiez left a comment (sagemath/pplpy#35) Is the boost check really necessary in the configure script of sage?

If boost is not installed, then meson will just disable the one module that actually relies on it. So I would say it would be fine to just print a warning message, and not exit forcefully with an error.

There are more spkgs in sage-distro which need boost, so it's better be there.

[tobiasdiez]

I tried building/testing (python3 -m pip install . --user, and testing with pytest) this in Homebrew, with Homebrew Python3.14, with PATH etc set as if we do to build sage-distro (after running source .homebrew-build-env) and it all works.

Thanks for testing. I have no idea what then really triggers this issue. Strangely, it also works on macos-15-intel.

This package does not depend upon Sage, there is absolutely no need to involve Sage in anything related to building its wheel etc. It's just like cysignals and cypari in this sense.

Sage-the-distro is used to build gmp, mpfr and mpc, which are needed for building the package/wheel.

I would say this PR is then good to go; will try to remove the dependency on sage-the-distro in #34 (using meson's subprojects).

[dimpase]

Same issue also on Linux Alpine (boost not found, but installed).

we don't really test Sage on Alpine. I gather it might be fixed by the following Sage patch (I'll do a PR to add it)

--- a/build/pkgs/_prereq/distros/alpine.txt
+++ b/build/pkgs/_prereq/distros/alpine.txt
@@ -23,3 +23,4 @@ bzip2
 pkgconf
 zlib-dev
 boost
+boost-dev

[dimpase]

On macOS, the problems must be due to the need for source .homebrew-build-env before ./boostrap && ./configure for using Homebrew. On Intel, Homebrew installs stuff in /usr/local, which is, by accident, good enough for ./configure to detect boost (it's done by a custom upstream m4 macro). On arm64, Homebrew is in /opt/homebrew (this, and /usr/local as you might know, are generically $(brew --prefix)), and the custom m4 macro fails, as it doesn't know where the headers are.
Perhaps

./configure --with-boost=$(brew --prefix) ...

would suffice - but I don't know how to incorporate this.
Sourcing .homebrew-build-env - which sets

export LIBRARY_PATH
export CPATH

would be better, as it would take care of all the package paths/configs.

[dimpase]

I'd try re-factoring the CIBW_BEFORE_ALL stuff in the way done in
https://github.com/dimpase/primecountpy/blob/master/.github/workflows/wheels.yml
There you can add commands per arch in a sane way.

[dimpase]

OK, please use notes I made here in #34