On Thu, Nov 6, 2025 at 6:59 PM Stefan van der Walt <[email protected]> wrote:
> On Mon, Nov 3, 2025, at 12:29, Nathan via NumPy-Discussion wrote: > > Ralf rightly pointed out ( > https://github.com/numpy/numpy/pull/30098#pullrequestreview-3408343827) > that np.fix does have substantial downstream usage and that a deprecation > needs to go through the mailing list, so I'm raising this here. > > > I see 9.2k files showing up in the GH search results, so in this instance > I'd say it's OK to remove it from the public namespace to discourage use, > but we probably shouldn't get rid of it? Perhaps just reimplement it using > np.trunc and leave it in place indefinitely? > The deprecation PR already reimplements it in terms of np.trunc, along with adding the deprecation. I think what I have in mind works out to effectively the same thing. I don’t expect to remove np.fix before numpy 3.0. The NumPy 2.0 transition showed that managing removals like that isn’t impossible. At the end of the day I think we also have machinery for removed API items so that the AttributeError people see will tell them that np.fix used to be in the API and to use np.trunc instead. > Stéfan > >
_______________________________________________ NumPy-Discussion mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/numpy-discussion.python.org Member address: [email protected]
