summaryrefslogtreecommitdiff
path: root/numpy/testing/_private
Commit message (Collapse)AuthorAgeFilesLines
* DOC: Avoid using "set of" when talking about an ordered list.Antony Lee2020-12-291-1/+1
| | | | | | | | | | | | ... or when the input isn't/cannot be a set. I left a few usages, e.g. in random sampling, where "set" is reasonable as informal description of an array as the order doesn't matter; however, for e.g. np.gradient the order of the returned list is clearly important, so "set" is wrong. Also some other minor doc edits noticed during the grepping: using `shape` instead of `form` in `cov` is consistent with most other places; the wording in `Polynomial.trim` now matches other methods on the same class.
* Merge pull request #18051 from rpolley/deprecate-np-testing-dec-2Matti Picus2020-12-291-0/+47
|\ | | | | DEP: deprecate np.testing.dec
| * DEC: update deprecation version to 1.21 and add date commentsRyan Polley2020-12-201-12/+18
| |
| * DEC: deprecate the decorators in np.testing.decRyan Polley2020-12-201-0/+41
| | | | | | | | | | | | Since the decorators in np.testing.dec are intended for nose test framework support, deprecate them by updating the docstring and adding a warning when they are used on functions
* | DOC: Fix a couple of reference to verbatim and vice versaMatthias Bussonnier2020-12-181-1/+1
|/ | | | | | | | | | | | | | | | This update a coupe of references (single backticks) that actually are not to verbatim/code (double backticks); and a couple of verbatim to reference when they do actually exists and can be resolved in context. I probably missed other; and stayed simple but spoted a few other inconsistencies that I did not fix: - some ``...`` could actually be :math:`...` but not always clear if it would be better. - some intervals are [``...``], other are ``[...]`` I guess they could be discussed individually; it was mostly the failing references that bothered me.
* Fix AttributeError: 'bool' object has no attribute 'ndim'Christoph Gohlke2020-12-031-1/+1
|
* minor typographic changeJakob2020-10-241-1/+1
|
* more fixesJakob2020-10-231-4/+4
|
* fix quotation marksJakob2020-10-231-1/+1
|
* fix typoJakob2020-10-231-1/+1
|
* mostly string conversionsJakob2020-10-235-57/+53
|
* TST: fix tests for windows + PyPymattip2020-07-301-1/+2
|
* TST: Add new tests for array coercion (#16571)Sebastian Berg2020-06-191-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * ENH: Add traceback-skip to `assert_array_compare` * TST: Add tests for arraycoercion These tests have many xfails (some technically maybe not correct), which describe in detail what will change when merging the array-coercion changes; since all of those xfails are going to be removed. * TST: Add test for empty sequences * TST: Add tests for bad self-mutating sequence inputs to np.array These should never happen and rightly should lead to undefined behaviour (and preferably errors), but they excercise some more tricky code branches and should probably not crash. * Simplify the "all scalars" logic (hardcode) and fix complex cases * MAINT: Some cleanup, and xfail pypy PyPy seems to have issues with int(numpy_complex), maybe because it gives a warning during conversion (python does not define it). So simply mark it as xfail, it should work in my branch. Also some smaller cleanups. * TST: Add some further test, re-add missing rational * MAINT: Make rationals optional, because they fail some tests currently The failures will go away, since this must again be related to implemetning int() and float(). * Update numpy/conftest.py * MAINT: Fix strings and use pytest.param to clean things up * TST: Add tests for 0-D array-like input to np.array() corner-cases * TST: Improve parameterization IDs to get better printing at -vv
* DOC: Fixes for 18 broken links (#16472)bjnath2020-06-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * DOC: Fixes for 18 broken links This, with PR #16465, should fix nearly all the remaining broken links on the site. 4 or 5 others should be easy to fix and just need attention from someone more knowledgeable -- will open an issue. For release notes with dead links, I could usually find links on archive.org for roughly contemporary versions. * DOC: Update to "Fixes for 18 broken links #16472" * Obsolete links, previously commented out, now deleted: https://github.com/numpy/numpy/pull/16472#discussion_r433928958 * Semantic markup for reference to Python class: https://github.com/numpy/numpy/pull/16472#discussion_r433553928 * Missing :ref: in internal link: https://github.com/numpy/numpy/pull/16472#discussion_r433554484 Not included: Resolution on using external/internal doc link in .py: https://github.com/numpy/numpy/pull/16472#discussion_r433554824 * DOC: Add internal link for 'Fixes for 18 broken links' PR #16472 Making reference [1] an internal link in function_base.py => numpy.vectorize.html * DOC: Redirect 2 link fixes in PR #16472 * governance.rst link reverted * ununcs.rst `overridden` link goes where it was meant to per https://github.com/numpy/numpy/pull/16472#pullrequestreview-424666070
* DOC: Improve assert_warns docstring with exampleSeth Troisi2020-06-011-3/+16
|
* DOC: Update assert_warns parameter listSeth Troisi2020-05-281-5/+3
|
* DOC: Add missing bracket (gh-16051)Chunlin2020-04-252-3/+3
| | | 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
|
* MAINT: cleanup unused imports; avoid redefinition of importsMike Taves2020-02-061-1/+0
| | | | | | | * Cleanup unused imports (F401) of mostly standard Python modules, or some internal but unlikely referenced modules * Where internal imports are potentially used, mark with noqa * Avoid redefinition of imports (F811)
* 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 'yield from <expr>' for simple cases (#15444)Mike Taves2020-01-271-2/+1
| | | | | | | | | This PR uses simple cases of PEP 380 to rewrite: for v in g: yield v into: yield from <expr>
* MAINT: Remove Python2 workaroundsSeth Troisi2020-01-231-3/+0
|
* MAINT: Replace basestring with str.Charles Harris2020-01-231-3/+2
| | | | | | | This replaces basestring with str except in - tools/npy_tempita/ - numpy/compat/py3k.py
* MAINT: Revise imports from collections.abc moduleMike Taves2020-01-221-9/+4
|
* STY: use `with open` when possibleSeth Troisi2020-01-211-6/+4
|
* MAINT: Remove sys.version checks in testsSeth Troisi2020-01-152-21/+2
|
* Merge pull request #15307 from sethtroisi/sys_version_preMatti Picus2020-01-161-49/+8
|\ | | | | MAINT: cleanup sys.version dependant code
| * MAINT: cleanup sys.version dependant codeSeth Troisi2020-01-121-49/+8
| |
* | TST: move _no_tracing to testing._privatemattip2020-01-151-0/+21
|/
* MAINT: Remove python2 array_getslice and array_setslice (#15263)Seth Troisi2020-01-071-2/+0
| | | These implemented the __getslice__ and __setslice__ methods in Python 2, which no longer exist in Python 3.
* Merge pull request #15256 from eric-wieser/use-keyword-only-argumentsMatti Picus2020-01-061-2/+1
|\ | | | | MAINT: Implement keyword-only arguments as syntax
| * 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 references to non-existent sys.exc_clear()Jon Dufresne2020-01-051-3/+0
|/ | | | | sys.exc_clear() was removed in Python 3. All internal uses can be removed.
* MAINT: Remove implicit inheritance from object class (#15236)Jon Dufresne2020-01-054-5/+5
| | | | | | | 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-034-8/+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
|/
* Fix typos, via a Levenshtein-style correctorBrian Wignall2019-12-191-1/+1
|
* 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-042-9/+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-012-0/+74
|
* 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
View Lorry Controller Status