Hi all, The subject of `MachAr` recently came up in https://github.com/numpy/numpy/pull/20132 and an earlier community meeting, more notably: it’s questionably role as public (and even private?) API. Ever since the introduction of hard-coded `finfo` parameters back in numpy/numpy#8504 there has been progressively less need for computing machine parameters during runtime, to the point where `MachAr` is effectively unused in the numpy codebase itself[1]. From a user-API point of view, the main difference between ` finfo` and `MachAr` these days is that the latter produces the same results roughly 4 orders of magnitude slower than the former… Are there any thoughts about deprecating it? Regards, Bas [1] It’s still used as fallback for `longdouble` types with unknown bytes-representations, rare cases that probably deserve their own pull request.
Hi, On Sat, Nov 6, 2021 at 4:54 PM Ralf Gommers <ralf.gommers@gmail.com> wrote:
I haven't looked at this code for a while - but is there any point in keeping it somewhere outside the NumPy codebase, for use when we hit an unusual e.g. longdouble type, and we want to infer `finfo`? My slight guess is no, that it's too unreliable in that case, and we'd be better off annotating the remaining code with suggestions to get this information. Cheers, Matthew
Hi, On Sat, Nov 6, 2021 at 4:54 PM Ralf Gommers <ralf.gommers@gmail.com> wrote:
I haven't looked at this code for a while - but is there any point in keeping it somewhere outside the NumPy codebase, for use when we hit an unusual e.g. longdouble type, and we want to infer `finfo`? My slight guess is no, that it's too unreliable in that case, and we'd be better off annotating the remaining code with suggestions to get this information. Cheers, Matthew
participants (3)
-
bas van beek -
Matthew Brett -
Ralf Gommers