Opened 7 weeks ago
Closed 3 days ago
#70931 closed update (fixed)
py-scipy: Update to 1.14.1
| Reported by: | jolivetr | Owned by: | michaelld (Michael Dickens) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | Michael-P-Allen (Mike Allen) | |
| Port: | py-scipy |
Description
Dear scipy port maintainers,
Scipy is now up to 1.14.1 and I need some of the recent features. Although I could install it with pip, I don't like it and I'd really like an up-to-date scipy port. I tried upgrading the port myself, but I quickly hit some issues which I cannot seem to be able to solve myself.
For instance, there is a post extraction step in which the setup.py is moved to _setup.py and this file does not exist in the new version of scipy. Commenting this post extraction step in the Portfile (just to check) leads to additional issues regarding patching (it cannot apply the patch patch-allow-MP-boost.diff).
So there is my limit... Sorry for this, but I would love a recent scipy in macports.
Thanks a lot for the efforts!
Cheers,
Romain
Change History (7)
comment:1 Changed 7 weeks ago by ryandesign (Ryan Carsten Schmidt)
| Keywords: | Scipy upgrade removed |
|---|---|
| Owner: | set to michaelld |
| Status: | new → assigned |
| Summary: | Upgrade scipy to 1.14.1 → py-scipy: Update to 1.14.1 |
comment:2 Changed 7 weeks ago by reneeotten (Renee Otten)
I started looking at this (as well as an update of NumPy). If we can agree on dropping support for older systems and (older Python versions) then the update is likely quite straightforward. The first issue you're seeing is due to a switch to the meson build system and in earlier versions upstream still supplied a setup.py file for backwards-compatibility but has stopped doing so now. Initial attempts showed that old OSes did not really want to work with meson build system; I am not willing to spend my time of trying to keep that all working, but I would be willing to look at the update for upstream supported Python versions (3.10+ with the latest version, but we could more easily support older versions that can be build with meson, probably Python 3.9) and modern OSes. But dropping earlier subports will result in a lot of downstream work remove these subports for dependents as well.
I think that's the major hold up for someone to be motivated to look into this.
comment:3 Changed 7 weeks ago by jmroot (Joshua Root)
The other complication is that numpy 2 broke backward compatibility (#70251) and a lot of dependents need to be updated or patched as a result.
comment:4 follow-up: 5 Changed 7 weeks ago by jolivetr
Well, I am trying to update another port (py-obspy) to provide python3.12 subport, and the build bot can't seem to be able to build it for py38 and py39. Since support is over for py38, we could simply rule it out and I would not mind moving ahead and getting rid of py39.
However, I have no idea who makes that kind of decision at macports...
comment:5 Changed 7 weeks ago by reneeotten (Renee Otten)
Replying to jolivetr:
Well, I am trying to update another port (py-obspy) to provide python3.12 subport, and the build bot can't seem to be able to build it for py38 and py39. Since support is over for py38, we could simply rule it out and I would not mind moving ahead and getting rid of py39.
However, I have no idea who makes that kind of decision at macports...
Please refrain from commenting on tickets with a completely unrelated topic... this has nothing to do with py-scipy.
comment:6 Changed 7 weeks ago by Michael-P-Allen (Mike Allen)
| Cc: | Michael-P-Allen added |
|---|
comment:7 Changed 3 days ago by reneeotten (Renee Otten)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
We also hope updating scipy will resolve #70460.