summaryrefslogtreecommitdiff
path: root/doc/source/reference/c-api
diff options
context:
space:
mode:
authorwarren <warren.weckesser@gmail.com>2021-12-22 23:27:29 -0500
committerwarren <warren.weckesser@gmail.com>2021-12-22 23:27:29 -0500
commit7b9a4c3b88bc82f539d30c295d34345708392f58 (patch)
tree8daa9264615a5d603bc0251522b55fb47a2b911c /doc/source/reference/c-api
parent4c15ba7f0143778e37b7841b8ccd17b21c796b71 (diff)
downloadnumpy-7b9a4c3b88bc82f539d30c295d34345708392f58.tar.gz
DOC: Add PyArray_FailUnlessWriteable to the online C-API docs.
The text was copy-edited a bit, and the comments in the C file were updated to match the documentation in the .rst file. Closes gh-20623.
Diffstat (limited to 'doc/source/reference/c-api')
-rw-r--r--doc/source/reference/c-api/array.rst11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/source/reference/c-api/array.rst b/doc/source/reference/c-api/array.rst
index fb8acffe6..d2e873802 100644
--- a/doc/source/reference/c-api/array.rst
+++ b/doc/source/reference/c-api/array.rst
@@ -1623,6 +1623,17 @@ For all of these macros *arr* must be an instance of a (subclass of)
calculations in NumPy that rely on the state of these flags do not
repeat the calculation to update them.
+.. c:function:: int PyArray_FailUnlessWriteable(PyArrayObject *obj, const char *name)
+
+ This function does nothing and returns 0 if *obj* is writeable.
+ It raises an exception and returns -1 if *obj* is not writeable.
+ It may also do other house-keeping, such as issuing warnings on
+ arrays which are transitioning to become views. Always call this
+ function at some point before writing to an array.
+
+ *name* is a name for the array, used to give better error messages.
+ It can be something like "assignment destination", "output array",
+ or even just "array".
Array method alternative API
----------------------------