Bug 272347 - science/py-scipy: Update to 1.11.1
Summary: science/py-scipy: Update to 1.11.1
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-python (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-03 13:30 UTC by Wen Heping
Modified: 2023-07-07 06:58 UTC (History)
4 users (show)

See Also:
vishwin: maintainer-feedback+
antoine: exp-run+


Attachments
Update to 1.11.1 (1.14 KB, text/plain)
2023-07-03 13:30 UTC, Wen Heping
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wen Heping freebsd_committer freebsd_triage 2023-07-03 13:30:08 UTC
Created attachment 243181 [details]
Update to 1.11.1

Update to 1.11.1
Comment 1 Charlie Li freebsd_committer freebsd_triage 2023-07-03 13:36:48 UTC
May want to try USE_PYTHON=pep517, which uses devel/meson-python (I have 1.10.1 built this way). Probably don't need --fcompiler=gnu95 or any of the patches in files/ anymore.
Comment 2 Antoine Brodin freebsd_committer freebsd_triage 2023-07-06 07:22:59 UTC
Exp-run looks fine
Comment 3 commit-hook freebsd_committer freebsd_triage 2023-07-06 12:49:59 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=9dce8cdebaffec269734230be1f2aee0a68059da

commit 9dce8cdebaffec269734230be1f2aee0a68059da
Author:     Wen Heping <wen@FreeBSD.org>
AuthorDate: 2023-07-06 12:40:21 +0000
Commit:     Wen Heping <wen@FreeBSD.org>
CommitDate: 2023-07-06 12:41:56 +0000

    science/py-scipy: Update to 1.11.1

    PR:             272347
    Reported by:    wen@
    Exp-run by:     antoine@

 science/py-scipy/Makefile |  3 +--
 science/py-scipy/distinfo | 10 +++++-----
 2 files changed, 6 insertions(+), 7 deletions(-)
Comment 4 Wen Heping freebsd_committer freebsd_triage 2023-07-06 12:51:43 UTC
(In reply to Charlie Li from comment #1)
I committed this patch.
Next time I shall try USE_PYTHON=pep517.

wen
Comment 5 Dani I. 2023-07-07 06:39:17 UTC
I don't know what exp-run you did, but that should never have been good.....

py-scipy 1.11.x isn't compatible with python38 - see https://github.com/scipy/scipy/releases/tag/v1.11.0 -> "This release requires Python 3.9+ and NumPy 1.21.6 or greater."


The port is still configured for python 3.8:
https://cgit.freebsd.org/ports/tree/science/py-scipy/Makefile?id=9dce8cdebaffec269734230be1f2aee0a68059da#n35


And the build obviously fails:
===>  Configuring for py38-scipy-1.11.1
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "setup.py", line 33, in <module>
    raise RuntimeError("Python version >= 3.9 required.")
RuntimeError: Python version >= 3.9 required.
*** Error code 1
Comment 6 commit-hook freebsd_committer freebsd_triage 2023-07-07 06:47:12 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=b4fe869292e67789ea83a690f0ce8d1fb560d3d9

commit b4fe869292e67789ea83a690f0ce8d1fb560d3d9
Author:     Charlie Li <vishwin@FreeBSD.org>
AuthorDate: 2023-07-07 06:44:36 +0000
Commit:     Charlie Li <vishwin@FreeBSD.org>
CommitDate: 2023-07-07 06:44:36 +0000

    science/py-scipy: bump minimum Python to 3.9

    Python 3.8 is no longer supported.

    Reported by: Dani I
    PR: 272347

 science/py-scipy/Makefile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Comment 7 Charlie Li freebsd_committer freebsd_triage 2023-07-07 06:49:15 UTC
(In reply to Dani I. from comment #5)
exp-runs only cover so much, and in this case, Python 3.9 only, since it is the default version in the framework currently.
Comment 8 Dani I. 2023-07-07 06:52:41 UTC
Thanks for the fast reaction. py-scipy is needed for ~230 (according to FreshPorts) (run/build). Do you really think deprecating/removing it for Python 3.8 - which is still supported for over one year - is the way to go?
Comment 9 Charlie Li freebsd_committer freebsd_triage 2023-07-07 06:58:43 UTC
Individual Python packages have the discretion to support fewer Python versions than what the Python Project supports for any number of reasons. Such reasons may include limited developer/maintainer manpower against only the latest Python, older Python lacking crucial features that to continue supporting require ugly conditionals, etc. SciPy have always been rather conservative in their support matrix.

In general, academic/scientific/amateur radio software tend to have much narrower or exact support matrices, consumers be damned.