summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNathan Goldbaum <nathan.goldbaum@gmail.com>2023-05-16 09:50:40 -0600
committerNathan Goldbaum <nathan.goldbaum@gmail.com>2023-05-16 09:50:40 -0600
commit630c0895a3d72755a19464682f228170e995b33a (patch)
tree1b249bbac99d525351374f3f6ce22e65ade219f7
parenta4a951d2ba256f6a391ae6dca30bee2bb491a59f (diff)
downloadnumpy-630c0895a3d72755a19464682f228170e995b33a.tar.gz
DOC: clarify how inputs of PyArray_ResultType are used
-rw-r--r--doc/source/reference/c-api/array.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/source/reference/c-api/array.rst b/doc/source/reference/c-api/array.rst
index baebfdb02..e8eca0f80 100644
--- a/doc/source/reference/c-api/array.rst
+++ b/doc/source/reference/c-api/array.rst
@@ -1149,11 +1149,11 @@ Converting data types
.. versionadded:: 1.6
- This applies type promotion to all the inputs,
- using the NumPy rules for combining scalars and arrays, to
- determine the output type of a set of operands. This is the
- same result type that ufuncs produce. The specific algorithm
- used is as follows.
+ This applies type promotion to all the input arrays and dtype
+ objects, using the NumPy rules for combining scalars and arrays, to
+ determine the output type for an operation with the given set of
+ operands. This is the same result type that ufuncs produce. The
+ specific algorithm used is as follows.
Categories are determined by first checking which of boolean,
integer (int/uint), or floating point (float/complex) the maximum