while True:
Bill: "2D transpose is common so it should have a nice syntax"
Tim, Robert, Sasha, and Ed: "No it's not."
Very well. I think it may be a self fulfilling prophecy, though. I.e. if matrix operations are cumbersome to use, then -- surprise surprise -- the large user base for matrix-like operations never materializes. Potential converts just give numpy the pass, and go to Octave or Scilab, or stick with Matlab, R or S instead.
Why all the fuss about the .T? Because any changes to functions (like making ones() return a matrix) can easily be worked around on the user side, as has been pointed out. But as far as I know -- do correct me if I'm wrong -- there's no good way for a user to add an attribute to an existing class. After switching from matrices back to arrays, .T was the only thing I really missed from numpy.matrix.
I would be all for a matrix class that was on equal footing with array and as easy to use as matrices in Matlab. But my experience using numpy.matrix was far from that, and, given the lack of enthusiasm for matrices around here, that seems unlikely to change. However, I'm anxious to see what Ed has up his sleeves in the other thread.
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Numpy-discussion mailing list Numpy-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion
