On Mon, Jan 2, 2017 at 7:26 PM, <josef.p...@gmail.com> wrote: > > > On Mon, Jan 2, 2017 at 9:00 PM, Ralf Gommers <ralf.gomm...@gmail.com> > wrote: > >> >> >> On Tue, Jan 3, 2017 at 2:36 PM, Charles R Harris < >> charlesr.har...@gmail.com> wrote: >> >>> Hi All, >>> >>> Just throwing this click bait out for discussion. Now that the `@` >>> operator is available and things seem to be moving towards Python 3, >>> especially in the classroom, we should consider the real possibility of >>> deprecating the matrix type and later removing it. No doubt there are old >>> scripts that require them, but older versions of numpy are available for >>> those who need to run old scripts. >>> >>> Thoughts? >>> >> >> Clearly deprecate in the docs now, and warn only later imho. We can't >> warn before we have a good solution for scipy.sparse matrices, which have >> matrix semantics and return matrix instances. >> >> Ralf >> > > How about dropping python 2 support at the same time, then we can all be > in a @ world. > > The "@" operator works with matrices already, what causes problems is the combination of matrices with 1-D arrays. That can be fixed, I think. The big problem is probably the lack of "@" in Python 2.7. I wonder if there is any chance of getting it backported to 2.7 before support is dropped in 2020? I expect it would be a fight, but I also suspect it would not be difficult to do if the proposal was accepted. Then at some future date sparse could simply start returning arrays.
Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
