Hi, On Tue, Jun 25, 2019 at 10:57 AM Stephan Hoyer <sho...@gmail.com> [snip] ... > I also agree with Alan that probably it's too late to change the behavior of > .T for arrays with more than 2-dimensions. NumPy could certainly use a more > comprehensive policy around backwards compatibility, but we certainly need to > meet a *very* high bar to break backwards compatibility. I am skeptical that > the slightly cleaner code facilitated by this new definition for .T would be > worth it. >
I feel strongly that we should have the following policy: * Under no circumstances should we make changes that mean that correct old code will give different results with new Numpy. On the other hand, it's OK (with a suitable period of deprecation) for correct old code to raise an informative error with new Numpy. That means that a.T deprecation -> a.T error -> a.T means a.MT is forbidden, but a.T deprecation -> a.T error is OK. Cheers, Matthew _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
