| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Revert "Merge pull request #7001 from shoyer/NaT-comparison"
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 7141f40b58ed1e7071cde78ab7bc8ab37e9c5983,
reversing changes made to 8fa6e3bef26a6d4a2c92f2824129aa4409be2590.
The original broke some pandas tests. The current plan to get this
in is
* reversion
* issue FutureWarning in 1.11 and 1.12
* make the change in 1.13.
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
| |
Now, NaT compares like NaN:
- NaT != NaT -> True
- NaT == NaT (and all other comparisons) -> False
We discussed this on the mailing list back in October:
https://mail.scipy.org/pipermail/numpy-discussion/2015-October/073968.html
|
| |
|
|\
| |
| | |
ENH: Tempfile context manager
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Context manager intended for use when the same temporary file needs to
be opened and closed more than once. The context manager creates the
file, closes it, and returns the path to the file. On exit from the
context block the file is removed. The file should be closed before
exiting the context as an error will be raised on windows if not.
Also fix up the `tempdir` context manager to deal with exceptions.
Tests are added for both `temppath` and `tempdir`.
|
|/
|
|
| |
Closes gh-6863.
|
|
|
|
|
|
|
|
| |
* use SkipTest in numpy tests instead of importing it from nose
* add a KnownFailureException as an alias for KnownFailureTest
(the former is preferred, but the latter is kept for backcompat)
* rename the KnownFailure nose plugin into KnownFailurePlugin,
and keep the old name for backcompat
|
| |
|
| |
|
|\
| |
| | |
ENH: Hide testing helper tracebacks when using them with pytest
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
function listed in __all__ for numpy/testing/utils.py.
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ndarray richcompare function has special case code for handling
void dtypes (esp. structured dtypes), since there are no ufuncs for
this. Previously, we would attempt to call the relevant
ufunc (e.g. np.equal), and then when this failed (as signaled by the
ufunc returning NotImplemented), we would fall back on the special
case code. This commit moves the special case code to before the
regular code, so that it no longer requires ufuncs to return
NotImplemented.
Technically, it is possible to define ufunc loops for void dtypes
using PyUFunc_RegisterLoopForDescr, so technically I think this commit
changes behaviour: if someone had registered a ufunc loop for one of
these operations, then previously it might have been found and
pre-empted the special case fallback code; now, we use the
special-case code without even checking for any ufunc. But the only
possible use of this functionality would have been if someone wanted
to redefine what == or != meant for a particular structured dtype --
like, they decided that equality for 2-tuples of float32's should be
different from the obvious thing. This does not seem like an important
capability to preserve.
There were also several cases here where on error, an array comparison
would return a scalar instead of raising. This is supposedly
deprecated, but there were call paths that did this that had no
deprecation warning. I added those warnings.
|
|
|
|
|
|
|
| |
Add context manager for tests that, on entry, clears record of any
previous warnings from given modules, so that any warning raised in the
context block does get raised, rather than suppressed by a previous
warning causing an entry in the `__warningregistry_`` of the module.
|
|
|
|
|
| |
Fixed typos in docstrings were updated for functions where the parameter
names in the docstring didn't match the function signature.
|
| |
|
| |
|
|\
| |
| |
| | |
DOC: Fixed incorrect assert_array_almost_equal_nulp documentation
|
| |
| |
| |
| |
| |
| | |
The `max()` function previously used does not work with two array-like.
`maximum()` does, and is what is essentially used in the code
(`ref = nulp * np.spacing(np.where(ax > ay, ax, ay))`).
|
| |
| |
| |
| |
| | |
minimum requirement is python2.6, this allows removing a couple 2.3 and
2.4 checks.
|
|\ \
| | |
| | | |
BUG: fix array_almost_equal for array subclasses
|
| |/
| |
| |
| | |
introduced in gh-4105/ab04e1ae0e8eca717bc7e42f3b0a60c9ff764289
|
| | |
|
|\ \
| | |
| | | |
documentation updates
|
| |/
| |
| |
| |
| |
| |
| |
| | |
"Raise an assertion" was changed to "Raises an AssertionError" to clarify that
an exception named AssertionError will be raised.
Closes gh-4884
[ci skip]
|
|/ |
|
|
|
|
| |
Also fix example in testing that Sphinx saw as section header.
|
|\
| |
| | |
BUG: fix some errors raised when minlength is incorrect in np.bincount
|
| | |
|
| |
| |
| |
| |
| | |
This check is needed now that build_err_msg takes a precision argument,
which is only relevant if the things being compared are ndarrays.
|
|/
|
|
|
|
|
|
| |
assert_array_almost_equal now prints the number of digits that were
being compared in the test instead of always printing 8 (the default
for array_repr). This would lead to uninformattive error messages.
Fixes #2367
|
|
|
|
| |
Fixes #2552. Changes primary test expression in function.
|
| |
|
| |
|
|
|
|
|
|
| |
Casting y to an inexact type fixes problems such as
abs(MIN_INT) < 0, and generally makes sense since the allclose
logic is inherently for float types.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Boolean - is not well defined, especially the unary and
binary operator are not compatible. In general boolean
minus seems to have no real application and does not do
what might be expected.
All "allclose" type functions (numpy, tests, masked) have to
now check for boolean to avoid the deprecation warning. In
the future one could think about removing it again and just
allowing the upcast.
|
|
|
|
|
|
|
| |
Allows deferring evaluation until failure.
Used for blocked minmax test which evaluate array representations for
the error message many thousand times accumulating to a full second
useless runtime.
|
|
|
|
| |
improves test performance by about 15%
|
|
|
|
|
|
|
|
|
| |
Minimize alignment combinations to useful set with SSE, might need to
be revisited if we add AVX support.
Move large data test_zeros test to slow and drop the extremely slow
count_nonzero() call.
Rename gen_alignment_data to _gen_alignment_data (private) to reserve
right to change it, e.g. add min_size.
|
|
|
|
|
|
|
| |
Run the 2to3 ws_comma fixer on *.py files. Some lines are now too long
and will need to be broken at some point. OTOH, some lines were already
too long and need to be broken at some point. Now seems as good a time
as any to do this with open PRs at a minimum.
|
|
|
|
| |
Now is as good a time as any with open PR's at a low.
|
|
|
|
| |
Deprecate np.testing.importall - it's pointless and partially broken.
|
|
|
|
|
|
|
|
|
|
|
|
| |
WarningManager was a workaround for the lack of the with statement
in Python versions < 2.6. As those versions are no longer supported
it can be removed.
Deprecation notes are added to WarningManager and WarningMessage, but
to avoid a cascade of messages in third party apps, no warnings are
raised at this time, that can be done later.
Closes #3519.
|