> Do you have any responses to the arguments Ralf made back in 2018 in favor of doing nothing? I was looking at a couple of issues on histograms specifically, there are many issues, features, optimizations that are present in histogramdd and not in histogram and vice versa. I think histogram should just call histogramdd internally in future as I do not see any reasons (other than legacy issues like this one) why they should behave differently. Would help maintainance greatly too.
About the Ralf's, I am not sure if some consumers' code would be broken (if so, I think it would be very rare) just by this change, but isn't this behaviour easy to implement user-side anyways? They can implement this behaviour if they deem this necessary. I am not an experienced developer so I might be wrong though. > Add it to the pile of issues to think about for NumPy 3.0, if we ever decide to do that? I guess this is the safest option. Although this will take a long time and may be forgotten/uncared for again. is it possible to add a related tag on that github issue or I may open a PR about it so this will be surely looked for in 3.0? _______________________________________________ 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]
