summaryrefslogtreecommitdiff
path: root/doc/source/reference/c-api
diff options
context:
space:
mode:
authorChris Brown <cbrown@fico.com>2023-04-22 21:47:44 +0100
committerGitHub <noreply@github.com>2023-04-22 22:47:44 +0200
commit73632427206b1cc7ae05959c8c875604421e62b5 (patch)
tree71829170396033d738676a90823766cd08b73cea /doc/source/reference/c-api
parent988381eabf7456eba0017e6bfe7e1f5566d91b94 (diff)
downloadnumpy-73632427206b1cc7ae05959c8c875604421e62b5.tar.gz
DOC: Clarify that defining NPY_NO_DEPRECATED_API does not determine ABI compatibility (#23631)
Closes gh-23610 [skip ci]
Diffstat (limited to 'doc/source/reference/c-api')
-rw-r--r--doc/source/reference/c-api/deprecations.rst4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/source/reference/c-api/deprecations.rst b/doc/source/reference/c-api/deprecations.rst
index 5b1abc6f2..d805421f2 100644
--- a/doc/source/reference/c-api/deprecations.rst
+++ b/doc/source/reference/c-api/deprecations.rst
@@ -58,3 +58,7 @@ On compilers which support a #warning mechanism, NumPy issues a
compiler warning if you do not define the symbol NPY_NO_DEPRECATED_API.
This way, the fact that there are deprecations will be flagged for
third-party developers who may not have read the release notes closely.
+
+Note that defining NPY_NO_DEPRECATED_API is not sufficient to make your
+extension ABI compatible with a given NumPy version. See
+:ref:`for-downstream-package-authors`.