summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSebastian Berg <sebastianb@nvidia.com>2023-04-25 10:49:19 +0200
committerSebastian Berg <sebastianb@nvidia.com>2023-04-25 11:18:04 +0200
commitc62881fa55fc830d16ac46bb1b91663266a8d94f (patch)
tree4941d6ec770d8fcf0103bead775f71c1e0c8d28e /doc
parent1a2a1142198db34bd48532f3553c2db97a0f3985 (diff)
downloadnumpy-c62881fa55fc830d16ac46bb1b91663266a8d94f.tar.gz
DOC: Align default with what the NEP draft says
We have three choices: 1. Be compatible with limited API (oldest supported Python version) 2. Be compatible with everything on the same Python version (this) 3. Be strict and default to NEP 29 This just rephrases things to be 2. Because our API version was not bumped over the relevant time frame, it is actually also compatible with the first.
Diffstat (limited to 'doc')
-rw-r--r--doc/release/upcoming_changes/23528.compatibility.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/release/upcoming_changes/23528.compatibility.rst b/doc/release/upcoming_changes/23528.compatibility.rst
index 7cf439be2..e2a98dfed 100644
--- a/doc/release/upcoming_changes/23528.compatibility.rst
+++ b/doc/release/upcoming_changes/23528.compatibility.rst
@@ -3,7 +3,8 @@ Binaries build against the NumPy C API now with older NumPy versions
Starting with NumPy 1.25 when including NumPy headers, NumPy now
defaults to exposing a backwards compatible API.
This means that by default binaries such as wheels build against
-NumPy 1.25 will also work with NumPy 1.17.
+NumPy 1.25 will also work with NumPy 1.16 because it has the same API version
+as NumPy 1.19 which is the oldest NumPy version compatible with Python 3.9.
You can customize this behavior using::