Pass --with-python=sage-python23 to Singular configure

[slel]

Either singular should depend on the python package
or --without-python should be passed to configure. Otherwise the configure script may find some unexpected python version.

See sage-release discussion:

• https://groups.google.com/d/msg/sage-release/wL-vwH-5GIk/3YBJMuSKAgAJ

CC: @isuruf @slel @dimpase

Component: build

Keywords: Singular

Author: Matthias Koeppe

Branch: 68327e9

Reviewer: Dima Pasechnik

Issue created by migration from https://trac.sagemath.org/ticket/28676

[mkoeppe]

Branch: u/mkoeppe/singular-configure-python

[mkoeppe]

comment:2

This is a problem for anyone who has a python2.7 binary somewhere in PATH, for example in /usr/local/bin, coming from homebrew.

With the simple patch on this ticket, in a Python 3 build of Sage, this now gives:

[singular-4.1.1p2.p0] checking for --with-python... sage-python23
[singular-4.1.1p2.p0] checking whether sage-python23 version >= 2.4... yes
[singular-4.1.1p2.p0] checking whether sage-python23 version >= 3... too recent, skipping python interface!

---

New commits:

68327e9

28676: Pass --with-python=sage-python23 to Singular configure

[mkoeppe]

Author: Matthias Koeppe

[mkoeppe]

Commit: 68327e9

[dimpase]

comment:3

Looks good to me. As far as I understand, it has no effect on sagelib, only on possible use of Singular's python interface outside of sagelib.

[dimpase]

Reviewer: Dima Pasechnik

[kiwifb]

comment:4

Yes, there are no effects on sagelib. And as I remember py3 is not supported, so this interface will probably just die since upstream doesn't seem to be interested in porting it to a more recent python. Not that we should care.

[vbraun]

Changed branch from u/mkoeppe/singular-configure-python to 68327e9

[mkoeppe]

comment:6

Follow up in #25993 - where we change it to --without-python

[mkoeppe]

Changed commit from 68327e9 to none