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.
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com