summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authortakanori-pskq <takanori17h@gmail.com>2020-10-24 18:57:44 +0900
committertakanori-pskq <takanori17h@gmail.com>2020-10-24 18:58:36 +0900
commit15bb98cf3ea6a5d8449874acd808c096d27a604c (patch)
treec40e97a844213f440d1db1289d7eaaeaca477f81
parent14bb26753df4ca4ef42ecd830699433ed781cf9f (diff)
downloadnumpy-15bb98cf3ea6a5d8449874acd808c096d27a604c.tar.gz
DOC: Fixup for PR #17614
-rw-r--r--doc/source/reference/arrays.interface.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/source/reference/arrays.interface.rst b/doc/source/reference/arrays.interface.rst
index aee95ba5b..d0a1c06c4 100644
--- a/doc/source/reference/arrays.interface.rst
+++ b/doc/source/reference/arrays.interface.rst
@@ -63,7 +63,7 @@ This approach to the interface consists of the object having an
Tuple whose elements are the array size in each dimension. Each
entry is an integer (a Python :py:class:`int`). Note that these
integers could be larger than the platform ``int`` or ``long``
- could hold (a Python :py:class`int` is a C ``long``). It is up to the code
+ could hold (a Python :py:class:`int` is a C ``long``). It is up to the code
using this attribute to handle this appropriately; either by
raising an error when overflow is possible, or by using
``long long`` as the C type for the shapes.