To: Discussion of Numerical Python <[email protected]> Message-ID: <CAN06oV9E2Xsf=tgbyqgxpnt4lhan6twtbuyi8gagt-vg2qa...@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jul 24, 2013 at 8:53 AM, St?fan van der Walt <[email protected]> wrote: I agree. During the Numarray period, I developed a Matrix sub-class which provided:On Wed, Jul 24, 2013 at 2:15 AM, Chris Barker - NOAA Federal <[email protected]> wrote:On Tue, Jul 23, 2013 at 6:09 AM, Pauli Virtanen <[email protected]> wrote:The .H property has been implemented in Numpy matrices and Scipy's sparse matrices for many years.Then we're done. Numpy is an array package, NOT a matrix package, and while you can implement matrix math with arrays (and we do), having quick and easy mnemonics for common matrix math operations (but uncommon general purpose array operations) is not eh job of numpy. That's what the matrix object is for.I would argue that the ship sailed when we added .T already. Most users see no difference between the addition of .T and .H. # PropertiesI think H was in there too. All of this was lost when Travis came along with numpy. No thought was given to sparse matrices at that time. I would argue that, in some sense, it should be promoted. Perhaps it's better as a separate module.The matrix class should probably be deprecated and removed from NumPy in the long run--being a second class citizen not used by the developers themselves is not sustainable. And, now that we have "dot" as a method, there's very little advantage to it. St?fan Colin W. |
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
