diff options
Diffstat (limited to 'doc/source/reference')
| -rw-r--r-- | doc/source/reference/c-api/iterator.rst | 2 | ||||
| -rw-r--r-- | doc/source/reference/c-api/ufunc.rst | 2 | ||||
| -rw-r--r-- | doc/source/reference/random/parallel.rst | 4 | ||||
| -rw-r--r-- | doc/source/reference/swig.interface-file.rst | 2 |
4 files changed, 5 insertions, 5 deletions
diff --git a/doc/source/reference/c-api/iterator.rst b/doc/source/reference/c-api/iterator.rst index 83644d8b2..b4adaef9b 100644 --- a/doc/source/reference/c-api/iterator.rst +++ b/doc/source/reference/c-api/iterator.rst @@ -653,7 +653,7 @@ Construction and Destruction may not be repeated. The following example is how normal broadcasting applies to a 3-D array, a 2-D array, a 1-D array and a scalar. - **Note**: Before NumPy 1.8 ``oa_ndim == 0` was used for signalling that + **Note**: Before NumPy 1.8 ``oa_ndim == 0` was used for signalling that ``op_axes`` and ``itershape`` are unused. This is deprecated and should be replaced with -1. Better backward compatibility may be achieved by using :c:func:`NpyIter_MultiNew` for this case. diff --git a/doc/source/reference/c-api/ufunc.rst b/doc/source/reference/c-api/ufunc.rst index 2909ce9af..39447ae24 100644 --- a/doc/source/reference/c-api/ufunc.rst +++ b/doc/source/reference/c-api/ufunc.rst @@ -171,7 +171,7 @@ Functions `numpy.dtype.num` (built-in only) that the corresponding function in the ``func`` array accepts. For instance, for a comparison ufunc with three ``ntypes``, two ``nin`` and one ``nout``, where the - first function accepts `numpy.int32` and the the second + first function accepts `numpy.int32` and the second `numpy.int64`, with both returning `numpy.bool_`, ``types`` would be ``(char[]) {5, 5, 0, 7, 7, 0}`` since ``NPY_INT32`` is 5, ``NPY_INT64`` is 7, and ``NPY_BOOL`` is 0. diff --git a/doc/source/reference/random/parallel.rst b/doc/source/reference/random/parallel.rst index 7f0207bde..bff955948 100644 --- a/doc/source/reference/random/parallel.rst +++ b/doc/source/reference/random/parallel.rst @@ -28,8 +28,8 @@ streams. `~SeedSequence` avoids these problems by using successions of integer hashes with good `avalanche properties`_ to ensure that flipping any bit in the input -input has about a 50% chance of flipping any bit in the output. Two input seeds -that are very close to each other will produce initial states that are very far +has about a 50% chance of flipping any bit in the output. Two input seeds that +are very close to each other will produce initial states that are very far from each other (with very high probability). It is also constructed in such a way that you can provide arbitrary-sized integers or lists of integers. `~SeedSequence` will take all of the bits that you provide and mix them diff --git a/doc/source/reference/swig.interface-file.rst b/doc/source/reference/swig.interface-file.rst index 6dd74f4ec..a22b98d39 100644 --- a/doc/source/reference/swig.interface-file.rst +++ b/doc/source/reference/swig.interface-file.rst @@ -904,7 +904,7 @@ Routines * ``PyArrayObject* ary``, a NumPy array. - Require the given ``PyArrayObject`` to to be Fortran ordered. If + Require the given ``PyArrayObject`` to be Fortran ordered. If the ``PyArrayObject`` is already Fortran ordered, do nothing. Else, set the Fortran ordering flag and recompute the strides. |