This would be really good to remove the apparent confusion. Moreover, I think cleanly explaining why using "np.matrix" is not a good idea *before* announcing the news would encourage people to accept this decision along the way. That would greatly reduce the sporadic "the devs are deprecating stuff as they see fit without asking us" sentiment.
On Thu, Nov 30, 2017 at 6:00 PM, Marten van Kerkwijk < m.h.vankerkw...@gmail.com> wrote: > Moving to a subpackage may indeed make more sense, though it might not > help as much with getting rid of the hacks inside other parts of numpy > to keep matrix working. In that respect it seems a bit different at > least from weave. > > Then again, independently of whether we remove or release a separate > package, it is probably best to start by moving all tests involving > matrix to matrixlib/tests, so we can at least get a sense of what > hacks are actually present. > > -- Marten > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
