Changes between Initial Version and Version 2 of Ticket #28676


Ignore:
Timestamp:
Dec 28, 2019, 3:02:24 AM (3 years ago)
Author:
mkoeppe
Comment:

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:

68327e928676: Pass --with-python=sage-python23 to Singular configure

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #28676

    • Property Status changed from new to needs_review
    • Property Authors changed from to Matthias Koeppe
    • Property Cc dimpase added
    • Property Summary changed from Clarify Singular dependence on Python to Pass --with-python=sage-python23 to Singular configure
    • Property Priority changed from major to critical
    • Property Branch changed from to u/mkoeppe/singular-configure-python
    • Property Commit changed from to 68327e976c9bc65f60debd1a7022ccca9f4fb2a1
  • Ticket #28676 – Description

    initial v2  
    11Either singular should depend on the python package
    2 or `--without-python` should be passed to `configure`.
     2or `--without-python` should be passed to `configure`. Otherwise the configure script may find some unexpected python version.
    33
    44See sage-release discussion: