| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
* DOC: add new glossary terms
* DOC: link to python Ellipsis
* DOC: fixes from review
* DOC: fixes from review
* DOC: remove glossary items that belong to python
|
| |
|
| |
* DOC: use :py:data:True and :py:data:False
|
| | |
|
| |
|
|
| |
* DOC: Add missing imports, np prefix, fix printing, fix examples
Co-Authored-By: Eric Wieser <wieser.eric@gmail.com>
|
| |
|
|
| |
Fix linking error
|
| |
|
|
| |
Fixed linking error
|
| |
|
|
|
|
|
|
|
| |
Made references to each other for the following two indexing docs
https://docs.scipy.org/doc/numpy-1.15.0/user/basics.indexing.html
https://docs.scipy.org/doc/numpy-1.13.0/reference/arrays.indexing.html
closes #12195
|
| | |
|
| |
|
|
| |
[ci skip]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`Ellipsis` expands to make the selection tuple be consistent with the
number of dimensions of the array being indexed. The length of the
expanded selection tuple may not be equal to the number of dimensions
in the array due to `newaxis` objects or advanced indexing. This
commit fixes the docs to correctly explain the behavior of `Ellipsis`.
For example,
```python
>>> import numpy as np
>>> x = np.zeros((3, 3, 3))
>>> x[:, ..., :2, np.newaxis].shape
(3, 3, 2, 1)
>>> x[:, :, :2, np.newaxis].shape
(3, 3, 2, 1)
```
The `Ellipsis` expands to a single `:` so that the selection tuple can
index the 3-D array. The length of the expanded selection tuple is 4,
not 3 as the docs indicated before this commit.
|
| | |
|
| |
|
|
|
|
| |
Currently, arr[[None, 0]] and arr[(None, 0)] mean the same thing, yet arr[[0, 0]] and arr[(0, 0)] mean different things. This makes it super hard to make a subclass or duck array that behaves consistently with ndarray.
By deprecating this feature, we force downstream library code to stop using it, which in turn makes that library code use approaches that are easier to implement in subclasses and duck types.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
WRITEBACKIFCOPY (#9639)
* ENH: add API to resolve UPDATEONCOPY outside dealloc, test and use
* BUG: Fix usage of keyword "from" as argument name for "can_cast".
Also removed inconsistency between the second argument name
between documentation ("totype") and code ("to").
* UPDATEIFCOPY -> WRITEBACKIFCOPY, documentation
* fixes for review
* review2, fix new test
* fix new test for using self.assert_deprecated
* change deprecation logic as per review
* new logic exposed places where PyArray_ResolveWritebackIfCopy not called
* deprecate PyArray_XDECREF_ERR in favor of PyArray_DiscardWritebackIfCopy
* code review changes
* clean up merge cruft
* fix from review
* fixes from review
* extend the release note
|
| |
|
|
|
|
|
|
| |
On line 88 the default value for stop index 'j' in the basic slice syntax is i:j:k for negative values of k is given as -1
Line 88: and -1 for *k < 0* . If *k* is not given it defaults to 1. Note that
Proposing that this should be changed to -n-1:
Line 88: and *-n-1* for *k < 0* . If *k* is not given it defaults to 1. Note that
The issue was discussed and was approved by a project member see the following link :
https://github.com/numpy/numpy/issues/9010#issuecomment-298095768
|
| |
|
| |
Replaces getslice and setslice which have been removed.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Instances remain for NumpyVersion and Numpy.rec.fromarrays that are
references to code.
Release notes were left unchanged.
see issue #7986
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Update docs for boolean array indexing and nonzero order.
Add links to row-major and column-major terms where they appear.
Closes #3177
|
| |
|
|
|
|
|
|
|
|
|
| |
This update adds a section better describing record arrays in the user
guide (numpy/doc/structured_arrays.py).
It also corrects nomenclature, such that "structured array" refers to
ndarrays with structured dtype, "record array" refers to modified
ndarrays as created by np.rec.array, and "recarray" refers to ndarrays
viewed as np.recarray. See the note at the end of the structured
array user guide.
|
| |
|
|
| |
closes gh-618
|
| |\
| |
| | |
DOC: Rework the advanced indexing documentation.
|
| | |
| |
| |
| |
| |
| | |
Mostly makes the advanced indexing doc much more example based,
and prominently mentions the np.ix_ function.
Some subtleties (some of which are new) are also mentioned.
|
| | | |
|
| |/ |
|
| |
|
|
|
| |
Mention in release notes and remove documentation which may
give the idea it cannot be used with advanced indexing.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
