summaryrefslogtreecommitdiff
path: root/numpy/testing/utils.py
Commit message (Collapse)AuthorAgeFilesLines
...
* MAINT: Minor code edits.chebee7i2015-02-221-1/+1
|
* ENH: Add `equal_nan` argument to allclose.chebee7i2015-02-201-2/+5
|
* Merge pull request #5374 from lebigot/patch-1Julian Taylor2014-12-241-1/+1
|\ | | | | | | DOC: Fixed incorrect assert_array_almost_equal_nulp documentation
| * DOC: Fixed incorrect assert_array_almost_equal_nulp documentationEric O. LEBIGOT (EOL)2014-12-241-1/+1
| | | | | | | | | | | | 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))`).
* | MAINT: remove obsolete version checksJulian Taylor2014-10-151-1/+1
| | | | | | | | | | minimum requirement is python2.6, this allows removing a couple 2.3 and 2.4 checks.
* | Merge pull request #5048 from juliantaylor/subclass-test-fixCharles Harris2014-09-041-1/+1
|\ \ | | | | | | BUG: fix array_almost_equal for array subclasses
| * | BUG: fix array_almost_equal for array subclassesJulian Taylor2014-09-051-1/+1
| |/ | | | | | | introduced in gh-4105/ab04e1ae0e8eca717bc7e42f3b0a60c9ff764289
* | BUG: fix percentage reporting when testing.assert_allclose fails.Patrick Peglar2014-08-311-1/+1
| |
* | Merge pull request #4905 from juliantaylor/doc-updateCharles Harris2014-07-271-7/+12
|\ \ | | | | | | documentation updates
| * | DOC: numpy.testing documentation clarification of "Raise an assertion"Austin Godber2014-07-271-7/+12
| |/ | | | | | | | | | | | | | | "Raise an assertion" was changed to "Raises an AssertionError" to clarify that an exception named AssertionError will be raised. Closes gh-4884 [ci skip]
* | Move tempdir context manager to numpy.testing.utilsOlivier Grisel2014-06-301-0/+16
|/
* DOC: fix examples in f2py documentation. They didn't appear at all in html.Ralf Gommers2014-04-211-1/+0
| | | | Also fix example in testing that Sphinx saw as section header.
* Merge pull request #4542 from immerrr/fix-bincount-systemerrorCharles Harris2014-03-261-1/+81
|\ | | | | BUG: fix some errors raised when minlength is incorrect in np.bincount
| * ENH: export nose.tools.assert_raises_regex via numpy.testing.utilsimmerrr2014-03-261-1/+81
| |
* | ENH: Add check for ndarray/scalar in build_err_msgYoshiki Vázquez Baeza2014-03-251-2/+10
| | | | | | | | | | This check is needed now that build_err_msg takes a precision argument, which is only relevant if the things being compared are ndarrays.
* | BUG:change formatting of assert_array_almost_equalYoshiki Vázquez Baeza2014-03-241-10/+10
|/ | | | | | | | 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
* ENH: Explicitly use __eq__ in assert_equal(a,b)Daniel da Silva2014-03-091-1/+3
| | | | Fixes #2552. Changes primary test expression in function.
* DOC: assert_no_warnings versionadded 1.8 -> 1.7alex2014-02-271-1/+1
|
* DOC: some versionadded notesalex2014-02-271-0/+7
|
* BUG: Force allclose logic to use inexact typeSebastian Berg2014-02-161-5/+9
| | | | | | 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.
* DEP: Deprecate boolean `-` operationsSebastian Berg2014-02-121-1/+6
| | | | | | | | | | | | 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.
* ENH: accept callable as message in assert_Julian Taylor2013-10-191-1/+6
| | | | | | | 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.
* TST: delay error message building to failures in assert_almost_equalJulian Taylor2013-09-241-6/+8
| | | | improves test performance by about 15%
* TST: speed up some very slow testsJulian Taylor2013-09-241-1/+1
| | | | | | | | | 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.
* STY: Giant comma spacing fixup.Charles Harris2013-08-181-20/+20
| | | | | | | 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.
* STY: Giant whitespace cleanup.Charles Harris2013-08-181-1/+0
| | | | Now is as good a time as any with open PR's at a low.
* MAINT: remove unused and broken parts of numpy.testingRalf Gommers2013-08-101-3/+11
| | | | Deprecate np.testing.importall - it's pointless and partially broken.
* MAINT: Remove uses of the WarningManager class.Charles Harris2013-07-121-17/+8
| | | | | | | | | | | | 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.
* MAINT: Use np.errstate context manager.Charles Harris2013-07-111-15/+5
| | | | | | | | | | | | | Now that Python < 2.6 is no longer supported we can use the errstate context manager in places where constructs like ``` old = seterr(invalid='ignore') try: blah finally: seterr(**old) ``` were used.
* DEP: Deprecate the oldnumeric and numarray modules.Charles Harris2013-06-101-0/+2
| | | | | | | | | The numarray and oldnumeric modules are deprecated. This is a bit tricky as raising a DeprecationWarning on import causes an error when tests are run. To deal with that, a ModuleDeprecationWarning class is added to numpy and NoseTester is modified to ignore that warning during testing. Closes #2905
* MAINT: fix shape mismatch issue in alignment data generatorJulian Taylor2013-06-081-4/+4
|
* ENH: vectorize sqrt ufunc using SSE2Julian Taylor2013-05-251-0/+67
| | | | | | | | | | | | | | | | | | specialize the sqrt ufunc for float and double and vectorize it using SSE2. improves performance by 4/2 for float/double if one is not memory bound due to non-cached data. performance is always better on all tested machines (amd phenom X2, intel xeon 5xxx/7xxx, core2duo, corei7) This version will not set errno on invalid input, but numpy only checks the fpu flags so the behavior is the same. In principle the compiler could autovectorize it when setting ffast-math (for no errno) and specializing the loop for the vectorizable strides and giving it some hints (restrict, __builtin_assume_aligned, etc.), but its simpler and more reliable to simply vectorize it by hand.
* 2to3: Apply types fixer.Charles Harris2013-04-141-4/+3
| | | | | | | | | | | | | | | | | | | | Python 3 removes the builtin types from the types module. The types fixer replaces such references with the builtin types where possible and also takes care of some special cases: types.TypeNone <- type(None) types.NotImplementedType <- type(NotImplemented) types.EllipsisType <- type(Ellipsis) The only two tricky substitutions are types.StringType <- bytes types.LongType <- int These are fixed up to support both Python 3 and Python 2 code by importing the long and bytes types from numpy.compat. Closes #3240.
* 2to3: Apply `map` fixer.Charles Harris2013-04-101-1/+2
| | | | | | | | | | | | | | | | | | | In Python 3 `map` is an iterator while in Python 2 it returns a list. The simple fix applied by the fixer is to inclose all instances of map with `list(...)`. This is not needed in all cases, and even where appropriate list comprehensions may be preferred for their clarity. Consequently, this patch attempts to use list comprehensions where it makes sense. When the mapped function has two arguments there is another problem that can arise. In Python 3 map stops execution when the shortest argument list is exhausted, while in Python 2 it stops when the longest argument list is exhausted. Consequently the two argument case might need special care. However, we have been running Python3 converted versions of numpy since 1.5 without problems, so it is probably not something that affects us. Closes #3068
* 2to3: Apply `repr` fixer.Charles Harris2013-04-081-4/+4
| | | | | | | | | | | | This replaces python backtics with repr(...). The backtics were mostly used to generate strings for printing with a string format and it is tempting to replace `'%s' % repr(x)` with `'%r' % x`. That would work except where `x` happened to be a tuple or a dictionary but, because it would be significant work to guarantee that and because there are not many places where backtics are used, the safe path is to let the repr replacements stand. Closes #3083.
* 2to3: Apply `print` fixer.Charles Harris2013-04-061-1/+1
| | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* Merge pull request #3191 from charris/2to3-apply-imports-fixerCharles Harris2013-04-061-2/+6
|\ | | | | 2to3: Apply `imports` fixer.
| * 2to3: Apply `imports` fixer.Charles Harris2013-04-021-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The `imports` fixer deals with the standard packages that have been renamed, removed, or methods that have moved. cPickle -- removed, use pickle commands -- removed, getoutput, getstatusoutput moved to subprocess urlparse -- removed, urlparse moved to urllib.parse cStringIO -- removed, use StringIO or io.StringIO copy_reg -- renamed copyreg _winreg -- renamed winreg ConfigParser -- renamed configparser __builtin__ -- renamed builtins In the case of `cPickle`, it is imported as `pickle` when python < 3 and performance may be a consideration, but otherwise plain old `pickle` is used. Dealing with `StringIO` is a bit tricky. There is an `io.StringIO` function in the `io` module, available since Python 2.6, but it expects unicode whereas `StringIO.StringIO` expects ascii. The Python 3 equivalent is then `io.BytesIO`. What I have done here is used BytesIO for anything that is emulating a file for testing purposes. That is more explicit than using a redefined StringIO as was done before we dropped support for Python 2.4 and 2.5. Closes #3180.
* | Merge pull request #460 from endolith/regex_formattingCharles Harris2013-04-031-1/+1
|\ \ | |/ |/| DOC: Formatting fixes using regex
| * DOC: Used regex to find colons missing spaces which render wrong online, ↵endolith2013-03-191-1/+1
| | | | | | | | also other spacing or formatting mistakes
* | 2to3: Use absolute imports.Charles Harris2013-03-281-2/+2
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new import `absolute_import` is added the `from __future__ import` statement and The 2to3 `import` fixer is run to make the imports compatible. There are several things that need to be dealt with to make this work. 1) Files meant to be run as scripts run in a different environment than files imported as part of a package, and so changes to those files need to be skipped. The affected script files are: * all setup.py files * numpy/core/code_generators/generate_umath.py * numpy/core/code_generators/generate_numpy_api.py * numpy/core/code_generators/generate_ufunc_api.py 2) Some imported modules are not available as they are created during the build process and consequently 2to3 is unable to handle them correctly. Files that import those modules need a bit of extra work. The affected files are: * core/__init__.py, * core/numeric.py, * core/_internal.py, * core/arrayprint.py, * core/fromnumeric.py, * numpy/__init__.py, * lib/npyio.py, * lib/function_base.py, * fft/fftpack.py, * random/__init__.py Closes #3172
* 2to3: Put `from __future__ import division in every python file.Charles Harris2013-03-011-0/+2
| | | | | | | | This should be harmless, as we already are division clean. However, placement of this import takes some care. In the future a script can be used to append new features without worry, at least until such time as it exceeds a single line. Having that ability will make it easier to deal with absolute imports and printing updates.
* Merge pull request #3056 from charris/2to3-filterCharles Harris2013-03-011-1/+1
|\ | | | | 2to3: Apply `filter` fixes. Closes #3053.
| * REF: Replace filters with list comprehensions.Charles Harris2013-02-281-1/+1
| | | | | | | | | | | | 2to3 does a lot of list(filter(...)) sort of thing which can be avoided by using list comprehensions instead of filters. This also seems to clarify the code to a considerable degree.
| * 2to3: Apply `filter` fixes. Closes #3053.Charles Harris2013-02-281-1/+1
| | | | | | | | | | Generally, this involves using list comprehension, or explicit list construction as `filter` is an iterator in Python 3.
* | 2to3: apply exec fixer results.Charles Harris2013-02-281-2/+2
|/ | | | This changes the `exec` command to the `exec` function.
* 2to3: Use modern exception syntax.Charles Harris2013-02-261-1/+1
| | | | Example: except ValueError,msg: -> except ValueError as msg:
* ENH: More capable test functions for warningsNathaniel J. Smith2012-09-201-3/+37
| | | | | | | 1) New function assert_no_warnings 2) Make assert_warns and assert_no_warnings pass through the function's return value on success, so that it can be checked as well.
* Remove maskna API from ndarray, and all (and only) the code supporting itNathaniel J. Smith2012-06-161-37/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The original masked-NA-NEP branch contained a large number of changes in addition to the core NA support. For example: - ufunc.__call__ support for where= argument - nditer support for arbitrary masks (in support of where=) - ufunc.reduce support for simultaneous reduction over multiple axes - a new "array assignment API" - ndarray.diagonal() returning a view in all cases - bug-fixes in __array_priority__ handling - datetime test changes etc. There's no consensus yet on what should be done with the maskna-related part of this branch, but the rest is generally useful and uncontroversial, so the goal of this branch is to identify exactly which code changes are involved in maskna support. The basic strategy used to create this patch was: - Remove the new masking-related fields from ndarray, so no arrays are masked - Go through and remove all the code that this makes dead/inaccessible/irrelevant, in a largely mechanical fashion. So for example, if I saw 'if (PyArray_HASMASK(a)) { ... }' then that whole block was obviously just dead code if no arrays have masks, and I removed it. Likewise for function arguments like skipna that are useless if there aren't any NAs to skip. This changed the signature of a number of functions that were newly exposed in the numpy public API. I've removed all such functions from the public API, since releasing them with the NA-less signature in 1.7 would create pointless compatibility hassles later if and when we add back the NA-related functionality. Most such functions are removed by this commit; the exception is PyArray_ReduceWrapper, which requires more extensive surgery, and will be handled in followup commits. I also removed the new ndarray.setasflat method. Reason: a comment noted that the only reason this was added was to allow easier testing of one branch of PyArray_CopyAsFlat. That branch is now the main branch, so that isn't an issue. Nonetheless this function is arguably useful, so perhaps it should have remained, but I judged that since numpy's API is already hairier than we would like, it's not a good idea to add extra hair "just in case". (Also AFAICT the test for this method in test_maskna was actually incorrect, as noted here: https://github.com/njsmith/numpyNEP/blob/master/numpyNEP.py so I'm not confident that it ever worked in master, though I haven't had a chance to follow-up on this.) I also removed numpy.count_reduce_items, since without skipna it became trivial. I believe that these are the only exceptions to the "remove dead code" strategy.
* ENH: missingdata: Finish count_nonzero as a full-fledged reduction operationMark Wiebe2011-08-271-16/+60
|
View Lorry Controller Status