summaryrefslogtreecommitdiff
path: root/numpy/lib/tests/test_io.py
Commit message (Collapse)AuthorAgeFilesLines
* TEST: on PyPy, skip hanging slow test [wheel build]mattip2022-05-021-0/+1
|
* TST: Skip unparsable field error tests on PyPySebastian Berg2022-01-191-0/+6
| | | | | | PyPy has a small bug with error formatting, so these cause it to crash. Simply skip the tests on old PyPy versions for now. (Matti fixed the issue long ago, just waiting for a new PyPy release :))
* TST,STY: Add small additional tests for converters/usecolsSebastian Berg2022-01-141-1/+1
| | | | | Also fix style a bit to silence linter (hopefully), removes some black style, but I am not too opinionated about that :)
* TST: Move most new loadtxt tests to its own fileSebastian Berg2022-01-141-767/+0
| | | | | | | | | | | | | | | | This also adds two basic new tests around files/strings containing the \0 character (prooving that we handle that gracefully). Also adds tests for: * the `_` thousands delimiter (should fail, but doesn't for float128 right now) * Failure modes when the number of rows changes (negative specifically) Many of these tests came originally from Warren Weckesser and others were added by Ross Barnowsky: Co-authored-by: Warren Weckesser <warren.weckesser@gmail.com> Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
* TST: Add test for hard/impossible to reach universal-newline support pathsSebastian Berg2022-01-141-0/+15
|
* TST: Improve test coverage, replace impossible error with assertSebastian Berg2022-01-141-0/+49
|
* TST,MAINT: New tests, byteswap cleanups and fixed assertSebastian Berg2022-01-141-6/+25
|
* TST,BUG: Additional bad-file-like test, add missing error path freeSebastian Berg2022-01-141-0/+14
| | | | And remove one silly leftover struct member that was unused
* MAINT,TST,BUG: Simplify streamer init, fix issues, and add testsSebastian Berg2022-01-141-0/+45
|
* ENH: Give warning for empty-lines not counting towards max-rowsSebastian Berg2022-01-141-0/+24
| | | | | | This also slightly cleans up the empty-line handling: previously we sometimes just had some extra empty-lines that just effectively never mattered
* MAINT: Move usecol handling to C and support more than integer colsSebastian Berg2022-01-141-2/+13
| | | | | | | | Of course to actually use that many columns you need A LOT of memory right now. Each field stores at least a UCS4 NUL character, but the field is padded enough to require 16 bytes. We always parse a full row, so that requires 20 bytes per field... (i.e. 32 GiB RAM is not enough to test this :)).
* TST: Add test to cover copyswap (byte-swap and unaligned)Sebastian Berg2022-01-141-0/+13
|
* BUG,TST: Add test for huge-float buffer path and ensure error returnSebastian Berg2022-01-141-0/+9
| | | | If a memory error happens, we should at least not crash the interpreter
* BUG: Fix complex parser and add tests for whitespace and failure pathsSebastian Berg2022-01-141-0/+27
|
* Add warning on empty file + tests.Ross Barnowski2022-01-141-4/+2
|
* Add UserWarning when reading no data.Ross Barnowski2022-01-141-0/+23
|
* rm incorrect comment.Ross Barnowski2022-01-141-1/+0
|
* Add tests for empty quotes and escaped quotechars.Ross Barnowski2022-01-141-0/+14
|
* TST: structured dtype w/ quotes.Ross Barnowski2022-01-141-0/+29
|
* Add tests for quote+multichar comments.Ross Barnowski2022-01-141-0/+23
| | | | Also correct exception message.
* Add test to check quoting support disabled by default.Ross Barnowski2022-01-141-0/+16
|
* TST: Add tests for quote character support.Ross Barnowski2022-01-141-0/+15
|
* TST: Fix test to align with stricter integer parsingSebastian Berg2022-01-141-24/+4
|
* TST: Small fixups for tests to make sure they pass againSebastian Berg2022-01-141-3/+3
|
* Port over tests from npreadtext test suiteRoss Barnowski2022-01-141-0/+484
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Add test for parsing scientific notation. - Add multiple-char comment test. - Port over tests for structured dtypes. - Add tests for exceptions on skiprows/max_rows. - port over ndmin tests. - Make structured data reusable, add unpack tests. - Port over delimiter tests. - Port over maxrows test w/ various dtypes. - Port over test of exception msg on parse failure. - Port over test for converters w/neg indices. - Port over usecols tests - Port over unicode tests. - Port over more converter tests. - Port over test for large rows. - Port over test for string-len discovery. - Port over float conversion accuracy test. - Port over bool test. - Add test for implicit float->int conversion. - Port over complex parsing tests. - Port over tests for reading from generator. - Port over object cleanup test. - Port over bytes incompat test. - Port over converters tests. Co-authored-by: Warren Weckesser <warren.weckesser@gmail.com> Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net>
* ENH: Raise an error for (most) stray newline charactersSebastian Berg2022-01-141-2/+2
| | | | | | | | This makes it strict that newline characters _within_ a single line (which is only possible if the user passes in a manual iterator of strings), is considered weird and rejected. An example is: `np.loadtxt(['1\n1', "2 2"], dtype=np.int64)`
* TST: Fixup current loadtxt tests for changesSebastian Berg2022-01-141-8/+7
|
* ENH: add ndmin to `genfromtxt` behaving the same as `loadtxt` (#20500)Ivan Gonzalez2021-12-161-0/+11
|
* BUG: Fix types of errors raised by genfromtxt (#20389)André Elimelek de Weber2021-12-031-0/+4
|
* MAINT: lib: Check that the dtype given to fromregex is structured.warren2021-09-221-0/+8
| | | | | | | | | | In fromregex, add a check that verifies that the given dtype is a structured datatype. This avoids confusing error messages that can occur when the given data type is not structured. Also tweaked the code in the Examples section. Closes gh-8891.
* ENH: Allow `np.fromregex` to accept `os.PathLike` implementationsBas van Beek2021-08-161-2/+4
|
* Rm numpy.lib.npyio.mafromtxt.Ross Barnowski2021-08-051-11/+0
|
* Rm numpy.lib.npyio.ndfromtxt.Ross Barnowski2021-08-051-11/+0
|
* PERF: Speed-up common case of loadtxt()ing non-hex floats. (#19598)Antony Lee2021-08-051-0/+22
| | | | | | | | | | | | | * PERF: Speed-up common case of loadtxt()ing non-hex floats. `python runtests.py --bench bench_io` reports a ~5-10% perf gain. * TST: Add tests to check fromhex not called unintentionally. Adds regression tests to check that the logic surrounding when the default floatconv applies the fromhex conversion does not change. Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
* fix from reviewmattip2021-01-241-2/+5
|
* TST: raise memory limit for testmattip2021-01-221-1/+1
|
* ENH: Allow genfromtxt to unpack structured arrays (#16650)Andrew Eckart2020-09-111-1/+46
| | | | | | | | | | | | | * ENH: Allow genfromtxt to unpack structured arrays genfromtxt failed to transpose output when unpack=True and `dtype` was structured (or None). This patch resolves the issue by returning a list of arrays, as in `loadtxt`. Co-authored-by: Matti Picus <matti.picus@gmail.com> Co-authored-by: Eric Wieser <wieser.eric@gmail.com> Co-authored-by: Sebastian Berg <sebastian@sipsolutions.net> Co-authored-by: Ross Barnowski <rossbar@berkeley.edu>
* MAINT: Remove users of `numpy.compat.bytes`Eric Wieser2020-08-311-1/+1
| | | | Some more Python 2 cleanup.
* TST: fix tests for windows + PyPymattip2020-07-301-1/+8
|
* TST, BUG: Re-raise MemoryError exception in test_large_zip's process (gh-16890)Antonio Larrosa2020-07-181-8/+22
| | | | | | | | | | | | Since #15893, test_large_zip's actual test is run in a child process, so when this test raises a MemoryError exception, the exception is lost and the @requires_memory decorator can't catch it to return an xfail. This commit uses a boolean variable in shared memory to flag if the exception was raised, and in that case, re-raise it in the parent process. Fixes #16889
* TST: Simplify assert_warns in test_io.pySeth Troisi2020-05-281-17/+8
|
* BUG: Fix default fallback in genfromtxtSebastian Berg2020-05-181-0/+7
| | | | | | | | | This affected (for example?) if the `dtype=object` was used without a converter, meaning that the default one is used. And this is currently the last one, which is `string_` (and thus bytes). Closes gh-16189
* TST: Add slow_pypy supportAnirudh Subramanian2020-04-131-0/+1
|
* TST: Run test_large_zip in a child process (#15893)Anirudh Subramanian2020-04-021-7/+12
| | | * Run test_large_zip in a child process
* BUG, TST: fix f2py for PyPy, skip one test for PyPy (#15750)Matti Picus2020-03-181-8/+9
| | | * BUG, TST: fix f2py for PyPy, skip one test for PyPy, xfail tests for s390x
* DEP: Do not allow "abstract" dtype conversion/creationSebastian Berg2020-02-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | These dtypes do not really make sense as instances. We can (somewhat) reasonably define np.dtype(np.int64) as the default (machine endianess) int64. (Arguably, it is unclear that `np.array(arr_of_>f8, dtype="f")` should return arr_of_<f8, but that would be very noisy!) However, `np.integer` as equivalent to long, is not well defined. Similarly, `dtype=Decimal` may be neat to spell `dtype=object` when you intend to put Decimal objects into the array. But it is misleading, since there is no special meaning to it at this time. The biggest issue with it, is that `arr.astype(np.floating)` looks like it will let float32 or float128 pass, but it will force a float64 output! Arguably downcasting is a bug in this case. A related issue is `np.dtype("S")` and especially "S0". The dtype "S" does make sense for most or all places where `dtype=...` can be passed. However, it is conceptionally different from other dtypes, since it will not end up being attached to the array (unlike "S2" which would be). The dtype "S" really means the type number/DType class of String, and not a specific dtype instance.
* MAINT: Python2 CleanupsSeth Troisi2020-01-211-3/+2
|
* NEP: issue deprecation warning when creating ragged array (NEP 34)Matti Picus2020-01-211-1/+1
| | | | This implements NEP 34.
* MAINT: Remove sys.version checks in testsSeth Troisi2020-01-151-11/+4
|
* MAINT: Remove implicit inheritance from object class (#15236)Jon Dufresne2020-01-051-8/+8
| | | | | | | 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.
View Lorry Controller Status