summaryrefslogtreecommitdiff
path: root/numpy/lib/tests/test_recfunctions.py
Commit message (Collapse)AuthorAgeFilesLines
* TST: Remove tests of view safety checks (see next commit)Allan Haldane2015-10-261-10/+0
| | | | | Remove unit tests for the view safety chekcs, which are to be reverted in the next commit.
* BUG: Fix imports in test_io.py and test_recfunctions.py.Charles Harris2015-07-041-3/+2
| | | | | | | | | Those test functions were incorrectly importing test functions from numpy/ma/testutils that were actually not defined there, but rather in numpy/testing. That did not cause an error when testutils was '*' importing all the test functions, but it was deceptive as some of the functions might appear to support masked arrays when they do not.
* ENH: structured datatype safety checksAllan Haldane2015-06-051-0/+30
| | | | | | | | | Previously views of structured arrays containing objects were completely disabled. This commit adds more lenient check for whether an object-array view is allowed, and adds similar checks to getfield/setfield Fixes #2346. Fixes #3256. Fixes #2599. Fixes #3253. Fixes #3286. Fixes #5762.
* MAINT: Fix problems noted by pyflakes in numpy/lib/tests.Charles Harris2014-07-311-16/+37
|
* STY: Make numpy/lib/test/*.py PEP8 compliant.Charles Harris2013-09-031-191/+190
| | | | | | | Run autopep8 over the test files in numpy/lib/test and make fixes to the result. Also remove Python5 workaround.
* STY: Giant comma spacing fixup.Charles Harris2013-08-181-7/+7
| | | | | | | 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.
* 2to3: Apply zip fixer.Charles Harris2013-04-131-12/+12
| | | | | | | | | | In Python 3 zip returns an iterator instead of a list. Consequently, in places where an iterator won't do it must be enclosed in list(...). Lists instead of iterators are also used in array constructors as using iterators there usually results in an object array containing an iterator object. Closes #3094
* 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.
* 2to3: Use absolute imports.Charles Harris2013-03-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* ENH: missingdata: Make numpy.all follow the NA && False == False ruleMark Wiebe2011-08-271-2/+2
|
* TST: rec: DType in join_by test was inconsistentMark Wiebe2011-07-191-2/+3
|
* BUG: Fixed bugs in join_by and added testsSkipper Seabold2011-07-081-3/+64
|
* STY: Replace assert by assert_ in tests. There remain 124 uses ofCharles Harris2011-04-051-2/+2
| | | | assert in non-testing files that should be checked for correctness.
* ENH: core: Shuffle type numbers so any new ones go on the end.Mark Wiebe2011-01-251-5/+18
|
* * Fixed merge_arrays for arrays of size 1 (bug #1407)pierregm2010-03-261-37/+46
| | | | * merge_arrays now accepts sequences of lists/tuples as inputs
* DEP: Fix deprecation warnings in Python 3.1. The warnings come from the unittestCharles Harris2010-02-201-2/+2
| | | | | | | | | module. The fix should be good for Python >= 2.4 and used the following sed script: s/\<failUnless\>/assertTrue/g s/\<failIf\>/assertFalse/g s/\<failUnlessEqual\>/assertEqual/g s/\<failUnlessRaises\>/assertRaises/g
* Fixed #1039: ignore sort order properly in find_duplicates testPauli Virtanen2009-03-301-8/+4
|
* Sort index of find_duplicated before testing, because the exact order is ↵David Cournapeau2009-03-091-17/+14
| | | | undefined for identical entries.
* Tag known failure on win32.David Cournapeau2009-02-191-0/+3
|
* * Added a 'autoconvert' option to stack_arrays.pierregm2009-02-021-1/+31
| | | | * Fixed 'stack_arrays' to work with fields with titles.
* * fixed a machine-dependent issue on default int ('<i4' on OS X, '<i8' on ↵pierregm2009-01-221-7/+10
| | | | | | linux) ? * fixed an machine-dependent issue on argsort ?
* * added recfunctions, a collection of utilities to manipulate structured arrays.pierregm2009-01-221-0/+570