On Mon, Feb 10, 2014 at 3:47 PM, Matthew Brett <matthew.br...@gmail.com> wrote: > Hi, > > On Mon, Feb 10, 2014 at 12:44 PM, Charles R Harris > <charlesr.har...@gmail.com> wrote: >> >> >> >> On Mon, Feb 10, 2014 at 1:23 PM, Alan G Isaac <alan.is...@gmail.com> wrote: >>> >>> On 2/10/2014 3:04 PM, Matthew Brett wrote: >>> > I teach psychologists and neuroscientists mainly >>> >>> >>> I must suspect that notebook was not for >>> **undergraduate** psychology students. >>> At least, not the ones I usually meet. >>> >>> SymPy is great but for those without background >>> it is at best awkward. It certainly does not >>> offer an equivalent to the notational convenience >>> of numpy's matrix object. >>> >>> >>> As far as I have been able to discern, the underlying >>> motivation for eliminating the matrix class is that >>> some developers want to stop supporting in any form >>> the subclassing of numpy arrays. Do I have that right? >>> >>> So the real question is not about numpy's matrix class, >>> but about whether subclassing will be supported. >>> (If I'm correctly reading the tea leaves.) >>> >> >> I don't see any reason to remove the Matrix object. It has its limitations, >> I don't use it myself, but it costs little and I don't see the value of >> forcing users to change. > > Maybe it would help to take 'remove the Matrix object' off the table > so we don't get side-tracked. Does anyone disagree with the proposal > to take that off the table?
No I really want to remove it :) If a non-frivolous NEP is written, this can be a token extreme opinion to be immediately discounted as not a practical solution. _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion