Repository navigation
Drop oldest-supported-numpy from build requirements when numpy 1.25 is released #14915
Description
@saimn said, "once 1.25 is out we can put it as minimum version in our build requirements," and drop oldest-supported-numpy. @seberg has also confirmed separately that this should work. cc @astropy/astropy-project-release-team
https://numpy.org/devdocs/release/1.25.0-notes.html#by-default-the-exported-numpy-c-api-is-now-compatible-with-numpy-1-19 (numpy/numpy#23528 and numpy/numpy#23872)
Line 5 in 0e4ab57
Reacted by Sebastian Berg
Reacted by Stuart Mumford
Activity
stefanv commentedon Jun 6, 2023
https://numpy.org/devdocs/dev/depending_on_numpy.html#build-time-dependency
pllim commentedon Jun 14, 2023
Do we want to do
#define NPY_TARGET_VERSION NPY_1_21_API_VERSIONto match this?astropy/setup.cfg
Line 31 in 23971c5
pllim commentedon Jun 14, 2023
On the conda-forge side, @mwcraig will have to decipher https://conda-forge.org/docs/maintainer/knowledge_base.html#building-against-numpy when the time comes.
pllim commentedon Jun 14, 2023
Does #14949 look about right or did I totally misunderstood?