| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Further progress in isolating matrix in preparation of its
deprecation. There is one place left with an explicit reference
to matrix (in MaskedArray.count), which is to be solved later.
|
| |
|
|
|
|
|
| |
That function is nose specific and has not worked since `__init__` files
were added to the tests directories.
|
|
|
|
|
|
|
|
| |
Numpy can now be tested using the standard
`python -c"import numpy; numpy.test()"`
construct.
|
|
|
|
|
|
|
|
|
|
|
| |
Use standard pytest markers everywhere in the numpy tests. At this point
there should be no nose dependency. However, nose is required to test
the legacy decorators if so desired.
At this point, numpy test cannot be run in the way with runtests, rather
installed numpy can be tested with `pytest --pyargs numpy` as long as
that is not run from the repo. Run it from the tools directory or some
such.
|
|
|
|
|
| |
The "bench" testing with the old bench files is no longer supported.
These days we use `runtests.py` and `asv`.
|
|\
| |
| | |
ENH: Add "stablesort" option to inp.sort as an alias for "mergesort".
|
| | |
|
| |
| |
| |
| | |
Closes #10784
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Depending on the input, this would return:
* A single slice, if mask=nomask
* A list of slices, if mask is an array
* None, if mask is fully masked
The documented return value is a list, and all downstream callers of this
function end up having to correct for it not being one.
This affects the result of np.ma.notmasked_contiguous, which also did not
document these unusual return values.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This removes a few left over uses of unittest. The main changes apart
from removal of Test case are:
* `setUp` replaced by nose and pytest compatible `setup`
* `tearDown` replaced by nose and pytest compatible `teardown`
* `assertRaises` replaced by `assert_raises`
* `assertEqual` replaced by `assert_equal`
The last two are in `numpy/testings/tests/test_utils.py`, so may seem a
but circular, but at least are limited to those two functions.
The use of `setup` and `teardown`, can be fixed up with the pytest
equivalents after we have switched to pytest.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Upload devdocs and neps after build
* Install numpydoc
* Fix masked array documentation injection
`doc_note` appends a `Notes` section to docstrings, which may lead to
duplicate sections.
* Add deploy key for neps repo
Note that we have to explicitly reset the ~/.ssh/config to only leave
one SSH key
* Only deploy on master branch
* Blow away previous dev docs after each upload
* Add tool to upload files to remote repo
* Remove numpydoc from pip install; it is included as a submodule
* Avoid using invalid escape code
* Rename repo upload tool
* Use check_call to simplify doc pushing tool
|
|
|
|
|
|
| |
By not using this type of indexing, it becomes easier for subclasses to override indexing in a way that works correctly with numpy functions.
These locations were found by deprecating the behavior in question, which is deliberately not part of this commit
|
|
|
|
|
|
|
|
|
| |
Currently, the `doc_note` function in `numpy.ma.core.py` is called to
add a "Notes" section to the existing docstrings of the unmasked
versions of some functions. This may result in duplicate "Notes"
sections, or incorrect placement, which are errors in current numpydoc.
This PR disables the `doc_note` function until we can decide on the
proper way to deal with the problem.
|
|
|
|
|
|
|
| |
with nin>2
There are no native ufuncs with this configuration.
Additionally, if there were, it would make more since for the domaining function to receive all the arguments, not reduce them pairwise.
|
|\
| |
| | |
BUG: Calling ufuncs with a positional output argument causes the result to inherit the output's mask
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
inherit the output's mask
This brings `np.add(a, b, out)` in line with `np.add(a, b, out=out)`.
These previously differed because gh-10459 causes them to call __array_wrap__ in different ways (with and without the output argument in the context tuple, respectively).
Since the data in the `out` argument is never used by ufuncs, it seems consistent that the mask should not be either.
|
| |
| |
| | |
[ci skip]
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
| |
Found via `codespell`
|
|\
| |
| | |
BUG: Masked singleton can be reshaped to be non-scalar
|
| |
| |
| |
| | |
It's possible this is the cause of gh-10270, where it seems something is wrong with the shape
|
|/ |
|
| |
|
|\
| |
| | |
BUG: Don't reimplement isclose in np.ma
|
| |
| |
| |
| | |
This fixes gh-10227, as well as some other problems that weren't previously known.
|
|\ \
| |/
|/| |
MAINT,ENH: remove MaskedArray.astype, as the base type does everything.
|
| |
| |
| |
| |
| | |
With a slight update to `__array_finalize__`, this also fixes the
mask ordering to be the same as that of the data.
|
| |
| |
| |
| |
| | |
Uses '_fromnxfunction_seq' just like 'vstack', 'hstack', etc.
Added release note to 1.15.0.
|
|\ \
| | |
| | | |
BUG: Fix broken format string picked up by LGTM.com
|
| | |
| | |
| | |
| | | |
Fixes regression I introduced in gh-10192
|
| |/
|/|
| |
| | |
Fixes gh-9233
|
|\ \
| |/
| | |
DEP: Deprecate the pickle aliases
|
| |
| |
| |
| |
| |
| | |
* The np.ma functions are misleading, as they do not actually do anything special for ma.array
* The np.loads functions doesn't even have numpy-specific documentation, and does not behave consistently with `np.load`
* The string overloads of np.ma.load and np.ma.dump do not work well on python 3, as they make assumptions about whether a binary or text pickle file is used (gh-5491)
|
|/ |
|
|
|
|
|
|
| |
Missed in gh-10176.
Already in the non-legacy branch, so no need to gate it here.
|
|
|
|
| |
Fixes #10059
|
|
|
|
|
|
|
| |
* Commas are now used within data and mask
* dtypes are shown for float32, int8 etc, where they previously weren't
* Wrapped fields are now correctly indented
* Spaces removed around = to match PEP8
|
| |
|
|
|
| |
Fixes #10045
|
| |
|
|
|
|
|
|
|
|
| |
np.set_string_function
It's more important that scalars and 0d arrays are consistent here.
Previously, unicode(arr0d) would crash on 2.7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
This means we can implement `__unicode__` easily too, or perhaps `__format__` in future
|
| |
|