On Tue, Feb 3, 2026 at 12:51 PM Michael Orlitzky <[email protected]> wrote: > > One of the ./configure checks for python is expecting the old format > for the license identifier in pyproject.toml, but all of the ones used > in sage have been updated. > > We probably shouldn't check this so soon because the sage distro > installs a newer setuptools anyway (is setuptools to blame?).
This is something that happens during the check of the system python, 3.12.3, with its setuptools. Do this mean that it fails its *own* checks? Or does it does check Sage's pyproject.toml, but this check is too old for our current pyproject.toml? I don't get what's going on here. Is 3.12.3 too old now for us? > Then > again, we probably probably should have python as a prereq instead of > the hundreds of lines of m4 macros currently used validate it. https://github.com/sagemath/sage/pull/41120 is moving python to prereqs (more precisely, even to bootstrap's prereqs) Dima > > Ref: > > 0. https://github.com/sagemath/sage/commit/df46f6e4 > 1. > https://packaging.python.org/en/latest/specifications/pyproject-toml/#license > > -- > 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 [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/sage-devel/aYJDktyjnOIGde62%40mertle. -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq0mW0Tuyzk0yu5ObZze%3Dz8g-FSTwzL59DxAzQ8zvWAcQQ%40mail.gmail.com.
