summaryrefslogtreecommitdiff
path: root/numpy/lib/user_array.py
diff options
context:
space:
mode:
authorMatthew Brett <matthew.brett@gmail.com>2017-02-03 20:02:09 +0000
committerCharles Harris <charlesr.harris@gmail.com>2017-02-03 13:02:09 -0700
commita611932bbcb132f82472a1f222a31e120fb6dc86 (patch)
tree39dd116f929a2f03be1c59d360e83827f28763af /numpy/lib/user_array.py
parenteefc4b8bea043a324927e40d998ed760799f0b82 (diff)
downloadnumpy-a611932bbcb132f82472a1f222a31e120fb6dc86.tar.gz
ENH: hard-code finfo parameters for known types (#8504)
* ENH: hard-code finfo parameters for known types Hard-code the MachAr parameters for float64, float32, 80-bit extended precision, to save time, and provide skeleton for more difficult types such as the double double on PPC; see https://github.com/numpy/numpy/issues/2669 * ENH: add PPC long double finfo Add parameters for PPC long double, fixing long-standing bug for finfo on PPC. * BF: use Python floats for float64 finfo For some reason (garrgh) np.exp2 with float64 gives a different answer on Windows than it does on other platforms; use Python floating point calculations instead, which do appear to be consistent. * DOC: add release notes for finfo fixes Add release note describing fixes for PPC long double ``finfo``. * RF: try using byte string to identify floats From suggestion by Chuck, and https//perl5.git.perl.org/perl.git/blob/3118d7d684b56cbeb702af874f4326683c45f045:/Configure * TST: add tests for reasonable finfo parameters Check that finfo returns somewhat reasonable parameters for all floating point types. * RF: add warning for not-recognized float type Warn if we don't have a signature for the float type. * NF: add IEEE float128 type signature Still needs test on platform with IEEE float128, to check MachAr-like parameters are correct.
Diffstat (limited to 'numpy/lib/user_array.py')
0 files changed, 0 insertions, 0 deletions