098dca3a9f
Use {!r} for a few other messages as well
2018-07-31 21:14:51 -03:00
bf7c188cc0
Improve error message for invalid types passed to pytest.approx()
...
* Hide the internal traceback
* Use !r representation instead of !s (the default for {} formatting)
2018-07-31 21:08:24 -03:00
d02491931a
Fix the unused import.
2018-07-31 11:33:46 -07:00
032db159c9
Let black reformat the code...
2018-07-31 11:23:23 -07:00
cd2085ee71
approx(): Detect type errors earlier.
2018-07-31 00:26:35 -07:00
ad305e71d7
Improve docstrings for Approx classes.
2018-07-30 23:26:57 -07:00
7d8688d54b
Reflect dimension in approx repr for numpy arrays.
2018-07-30 23:23:17 -07:00
bf127a63b2
Need to iterate over the flattened array.
2018-07-27 11:24:42 -07:00
d0ba242c46
Implement change suggested by @kalekundert in PR
2018-07-27 15:07:20 -03:00
f0db64ac2e
drop the duplicate approx call
...
update test to include both np.array(actual) and np.array(expected)
2018-07-24 21:18:44 -04:00
7bff5866b1
bugfix in ApproxNumpy initialisation, use keywords for arguments now
2018-07-18 17:29:55 -04:00
cbaa7dd56a
Upgrade pre-commit hooks except pyupgrade
2018-06-26 06:35:27 -07:00
0030ceb11c
Bug fix #3593 - approx method in a single element of numpy array
...
If the user pass as a expected value a numpy array created like
numpy.array(5); it will creates an array with one element without shape,
when used with approx it will raise an error
'TypeError: iteration over a 0-d array'
2018-06-25 22:55:16 +02:00
acb8f23311
Fix 2 DeprecationWarnings about invalid escape seq
2018-06-16 10:37:33 +02:00
eaa882f3d5
switch to src layout
2018-05-26 09:10:38 +02:00
Bruno Oliveira
Kale Kundert
abrammer
Alan
Anthony Sottile
Marcelo Duarte Trevisani
Hynek Schlawack
Ronny Pfannschmidt