https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277826
--- Comment #29 from Max Brazhnikov <[email protected]> --- (In reply to Charlie Li from comment #27) > Both the current upstream numpy and scipy have dropped Python 3.10 support. > The upstream Python project still supports 3.10 until later this year, so we > follow that. We can keep Python 3.10 in ports as long as we need it - hello lang/python27!. However this should not imply support for py310 flavors, otherwise we'll fall behind with newer versions. > But individual projects have the discretion of dropping older supported > versions earlier, which is what these two have done. We can follow upstream and drop 3.10 support in numpy and scipy ports. I doubt anybody cares about py310 flavors for scientific ports including these two ports. And as I mentioned earlier numpy@py310 already fails to build for other reason. > While current scipy can build with numpy 1, in reality numpy 2 is needed to > run. not really, SciPy devs state (https://github.com/scipy/scipy/blob/93d4114a3889c66121e90d36411e9159a64e6bd7/pyproject.toml#L25C1-L30C33): # numpy requirement for wheel builds for distribution on PyPI - building # against 2.x yields wheels that are also compatible with numpy 1.x at # runtime. # Note that building against numpy 1.x works fine too - users and # redistributors can do this by installing the numpy version they like and # disabling build isolation. > For free-threaded CPython, ie 3.13t (and soon 3.14t), at least numpy 2.1.3 is > required. Let's enable Python 3.12 first, than we'll look for more recent versions. > Some consumers specify both numpy and scipy rather than only scipy so the > numpy specified in this port has to match, which is where "situated" comes > from. > Also higher-order consumers may themselves specify numpy but not scipy. Charlie, what do you suggest exactly? Update numpy port to 2.x along with scipy update? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
