On Mon, Jan 2, 2017 at 6: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. > > Josef
Let's not yoke together two (mostly) unrelated controversial discussions? I doubt we'll be able to remove either Python 2 or matrix support before 2020 at the earliest, so the discussion now is just about how to communicate to users that they should not be using 'matrix'. -n -- Nathaniel J. Smith -- https://vorpus.org _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
