summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Wieser <wieser.eric@gmail.com>2020-08-26 09:38:22 +0100
committerGitHub <noreply@github.com>2020-08-26 09:38:22 +0100
commitada91e01ab0b44bd7af71c404c8b7020b2dce2bc (patch)
treeaf1ab54fa99f3df4095ac580f3438a41ad4d93e8
parentfe04c2aed76b068743ff4ad3c9ed01feb871cef2 (diff)
downloadnumpy-ada91e01ab0b44bd7af71c404c8b7020b2dce2bc.tar.gz
Wrap lines
-rw-r--r--doc/source/reference/arrays.interface.rst10
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/source/reference/arrays.interface.rst b/doc/source/reference/arrays.interface.rst
index c6da326d7..73e4aef0c 100644
--- a/doc/source/reference/arrays.interface.rst
+++ b/doc/source/reference/arrays.interface.rst
@@ -327,13 +327,15 @@ largely aesthetic. In particular:
Until August 2020, this said:
- Now it must be a tuple whose first element is a string with "PyArrayInterface Version #" and whose
- second element is the object exposing the array.
+ Now it must be a tuple whose first element is a string with
+ "PyArrayInterface Version #" and whose second element is the object
+ exposing the array.
This design was retracted almost immediately after it was proposed, in
<https://mail.python.org/pipermail/numpy-discussion/2006-June/020995.html>.
- Despite 14 years of documentation to the contrary, at no point was it valid
- to assume that ``__array_interface__`` capsules held this tuple content.
+ Despite 14 years of documentation to the contrary, at no point was it
+ valid to assume that ``__array_interface__`` capsules held this tuple
+ content.
3. The tuple returned from ``__array_interface__['data']`` used to be a
hex-string (now it is an integer or a long integer).