summaryrefslogtreecommitdiff
path: root/numpy/testing/_private/utils.py
Commit message (Collapse)AuthorAgeFilesLines
...
* DOC: Add missing bracket (gh-16051)Chunlin2020-04-251-2/+2
| | | Add missing closing brackets, script to generate the list in the PR gh-16051.
* BUG: fix doctest exception messagesmattip2020-02-281-5/+12
|
* DOC: Reword docstring for assert_equal (gh-15614)Harshal Prakash Patankar2020-02-191-1/+1
|
* BUG: Ignore differences in NAN representation for computing ULP differencesRaghuveer Devulapalli2020-02-181-2/+17
|
* STY,MAINT: avoid 'multiple imports on one line' (flake8 E401)Mike Taves2020-01-281-1/+3
| | | | | | * PEP 8: "Imports should usually be on separate lines" * Where modified, sort imported modules alphabetically * Clean-up unused imports from these expanded lines
* STY: use `with open` when possibleSeth Troisi2020-01-211-6/+4
|
* MAINT: Remove sys.version checks in testsSeth Troisi2020-01-151-12/+2
|
* TST: move _no_tracing to testing._privatemattip2020-01-151-0/+21
|
* MAINT: Implement keyword-only arguments as syntaxEric Wieser2020-01-061-2/+1
| | | | Now that 2.7 is gone, there is no need to pop manually from kwarg dictionaries.
* MAINT: Remove implicit inheritance from object class (#15236)Jon Dufresne2020-01-051-1/+1
| | | | | | | Inheriting from object was necessary for Python 2 compatibility to use new-style classes. In Python 3, this is unnecessary as there are no old-style classes. Dropping the object is more idiomatic Python.
* MAINT: Remove unnecessary 'from __future__ import ...' statementsJon Dufresne2020-01-031-2/+0
| | | | | As numpy is Python 3 only, these import statements are now unnecessary and don't alter runtime behavior.
* Merge pull request #15178 from rgommers/maxulp-msgCharles Harris2020-01-021-2/+3
|\ | | | | TST: improve assert message of assert_array_max_ulp
| * TST: improve assert message of assert_array_max_ulpRalf Gommers2019-12-261-2/+3
| | | | | | | | | | | | It was not showing the max difference before, which makes it hard to judge whether something is seriously wrong, or the test precision simply needs to be bumped by a little.
* | MAINT: better way of indicating whether numpy was built with ILP64 BLASPauli Virtanen2020-01-011-2/+2
|/
* ENH: update BLAS symbol suffix/prefix handling in cblasfuncs & linalgPauli Virtanen2019-12-141-1/+1
| | | | Revise the BLAS name mangling to support the general scheme.
* TST: testing: check requires_memory immediately before the test + ignore ↵Pauli Virtanen2019-12-081-1/+24
| | | | MemoryErrors
* TST: fix up issues in requires_memory decoratorPauli Virtanen2019-12-041-5/+6
| | | | Fix wrong multiplier for /proc/meminfo, and do style cleanups.
* TST: linalg: add smoke test for 64-bit blasPauli Virtanen2019-12-011-1/+3
|
* TST: add pytest machinery to specify memory requirements for testsPauli Virtanen2019-12-011-0/+70
|
* ENH: add isinf, isnan, fmin, fmax loops for datetime64, timedelta64 (#14841)Matti Picus2019-11-211-15/+27
| | | | | | | | `np.datetime('NaT')` should behave more like `float('Nan')`. Add needed infrastructure so `np.isinf(a)` and `np.isnan(a)` will run on `datetime64` and `timedelta64` dtypes. Also added specific loops for `numpy.fmin` and `numpy.fmax` that mask `NaT`.
* DOC: testing: Note handling of scalars in assert_array_equal and assert_equal.Warren Weckesser2019-11-201-5/+22
|
* assert_array_compareMaxwell Aladago2019-09-061-7/+8
|
* BUG: Fixed maximum relative error reporting in assert_allclose (gh-13802)CakeWithSteak2019-09-051-2/+7
| | | | | | Fixed maximum relative error reporting in assert_allclose: In cases where the two arrays have zeros at the same positions it will no longer report nan as the max relative error
* DEP: numpy.testing.rand (#14325)Maxwell Aladago2019-08-221-18/+1
| | | * Deprecation: numpy.testing.rand
* ENH: Improve mismatch message of np.testing.assert_array_equal (#14203)Tim Hoffmann2019-08-151-2/+5
| | | | | The original message included "Mismatch: 33.3%". It's not obvious what this percentage means. This commit changes the text to "Mismatched elements: 1 / 3 (33.3%)".
* MAINT: Replace integers in places where booleans are expectedMSeifert042019-07-011-1/+1
|
* MAINT: Misc. typo fixes (#13664)luzpaz2019-05-311-2/+2
| | | | | | * DOC, MAINT: Misc. typo fixes Found via `codespell`
* BUG: special case object arrays when printing rel-, abs-errormattip2019-05-271-4/+12
|
* Merge pull request #13518 from hmaarrfk/faster_array_compareEric Wieser2019-05-121-4/+3
|\ | | | | MAINT: implement assert_array_compare without converting array to python list
| * Ensure that reduced is a 1D arrayMark Harfouche2019-05-121-1/+1
| |
| * Fixup: address eric-wieser's commentsMark Harfouche2019-05-121-5/+3
| |
| * MNT: implement assert_array_compare without converting array to python list.Mark Harfouche2019-05-091-4/+5
| |
* | DOC: testing: Mention the handling of nan in the assert_equal docstring.Warren Weckesser2019-05-051-0/+10
|/
* DOC: defaults in allclose not the same as in assert_allclose (#13395)Dieter Werthmüller2019-04-251-3/+3
| | | * DOC: defaults in allclose not the same as in assert_allclose
* MAINT: move gc.collect to function (from review)mattip2019-04-191-1/+19
|
* DEV: add pypy3 to azure CImattip2019-04-161-0/+1
|
* ENH: add "max difference" messages to np.testing.assert_array_equal (#12591)Stephan Hoyer2019-01-011-82/+121
| | | | | | | | | | | | | | | | | | | | | | Example behavior: >>> x = np.array([1, 2, 3]) >>> y = np.array([1, 2, 3.0001]) >>> np.testing.assert_allclose(x, y) AssertionError: Not equal to tolerance rtol=1e-07, atol=0 Mismatch: 33.3% Max absolute difference: 0.0001 Max relative difference: 3.33322223e-05 x: array([1, 2, 3]) y: array([1. , 2. , 3.0001]) Motivation: when writing numerical algorithms, I frequently find myself experimenting to pick the right value of `atol` and `rtol` for `np.testing.assert_allclose()`. If I make the tolerance too generous, I risk missing regressions in accuracy, so I usually try to pick the smallest values for which tests pass. This change immediately reveals appropriate values to use for these parameters, so I don't need to guess and check.
* TST, DOC: enable refguide_checkTyler Reddy2018-12-141-3/+0
| | | | | | | | * ported the refguide_check module from SciPy for usage in NumPy docstring execution/ verification; added the refguide_check run to Azure Mac OS CI * adjusted NumPy docstrings such that refguide_check passes
* MAINT: Review F401,F841,F842 flake8 errors (unused variables and imports) ↵Roman Yurchak2018-12-061-3/+2
| | | | | | | | | | | | (#12448) * Review F401,F841,F842 flake8 errors (unused variables, imports) * Review comments * More tests in test_installed_npymath_ini * Review comments
* Merge pull request #12243 from liwt31/fix_misleading_msgMatti Picus2018-10-231-3/+6
|\ | | | | BUG: Fix misleading assert message in assert_almost_equal #12200
| * BUG: Fix misleading assert message in assert_almost_equal #12200wtli@Dirac2018-10-231-3/+6
| | | | | | | | | | Fixes #12200 by making a copy of the matrix before NaN's are excluded. Add a test for it.
* | ENH: __array_function__ support for np.lib, part 2/2 (#12119)Stephan Hoyer2018-10-221-11/+16
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * ENH: __array_function__ support for np.lib, part 2 xref GH12028 np.lib.npyio through np.lib.ufunclike * Fix failures in numpy/core/tests/test_overrides.py * CLN: handle depreaction in dispatchers for np.lib.ufunclike * CLN: fewer dispatchers in lib.twodim_base * CLN: fewer dispatchers in lib.shape_base * CLN: more dispatcher consolidation * BUG: fix test failure * Use all method instead of function in assert_equal * DOC: indicate n is array_like in scimath.logn * MAINT: updates per review * MAINT: more conservative changes in assert_array_equal * MAINT: add back in comment * MAINT: casting tweaks in assert_array_equal * MAINT: fixes and tests for assert_array_equal on subclasses
* MAINT: Make assert_array_compare more generic.Charles Harris2018-08-171-6/+15
| | | | | | | Use np.all instead of the *.all method to be a bit more robust against bad subclasses of ndarray that may change the behavior of the method. Closes #11743.
* BUG: Make assert_string_equal check str equality simply without regexSho Nakamura2018-07-141-2/+2
|
* HTTP -> HTTPS, and other linkrot fixesMike Toews2018-06-161-4/+4
|
* Merge pull request #11122 from mhvk/assert-array-comparison-with-maskedCharles Harris2018-06-071-41/+35
|\ | | | | BUG,MAINT: Ensure masked elements can be tested against nan and inf.
| * MAINT: clean up assert_array_compare a bit further.Marten van Kerkwijk2018-06-041-10/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This brought to light two bugs in tests, which are fixed here, viz., that a sample ndarray subclass that tested propagation of an added parameter was incomplete, in that in propagating the parameter in __array_wrap__ it assumed it was there on self, but that assumption could be broken when a view of self was taken (as is done by x[~flagged] in the test routine), since there was no __array_finalize__ defined. The other subclass bug counted, incorrectly, on only needing to provide one type of comparison, the __lt__ being explicitly tested. But flags are compared with __eq__ and those flags will have the same subclass.
| * BUG,MAINT: Ensure masked elements can be tested against nan and inf.Marten van Kerkwijk2018-05-271-38/+29
| | | | | | | | | | | | | | The removal of nan and inf from arrays that are compared using test routines like assert_array_equal treated the two arrays separately, which for masked arrays meant that some elements would not be removed when they should have been. This PR corrects this.
* | BUG: Import WarningMessage from warnings.Charles Harris2018-06-041-0/+1
| |
* | MAINT: Remove dead code backporting py2.6 warningsEric Wieser2018-06-041-92/+0
|/ | | | Since this is now in `np.testing._private`, it's no longer usable by the outside world anyway
View Lorry Controller Status