On 6/25/2019 11:03 AM, Todd wrote:
Fair enough. But although there are valid reasons to do a divide by zero, it still causes a warning because it is a problem often enough that people should be made aware of it. I think this is a similar scenario.
I side with Stephan on this, but when there are opinions on both sides, I wonder what the resolution strategy is. I suppose there is a possible tension: 1. Existing practice should be privileged (no change for the sake of change). 2. Documented user issues need to be addressed. So what is an "in the wild" example of where numpy users create errors that pass silently because a 1-d array transpose did not behave as expected? Why would the unexpected array shape of the result not alert the user if it happens? In your favor, Mathematica's `Transpose` raises an error when applied to 1d arrays, and the Mma designs are usually carefully considered. Cheers, Alan Isaac _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
