Pierre GM wrote: >> How far away is maskedarray from being able to replace numpy.ma? >> > > So far, it does everything that numpy.core.ma does, with I believe more > flexibility and some additional features (hard/soft mask, easy > subclassing...). Personally, I stopped using numpy.core.ma completely (unless > for test purposes), and I even managed to convince another user to switch to > this module for his own work (cf the TimeSeries package). > > Of course, I expect that there are still some bugs here and there, but I'm > working on it (when I find them). It's a tad slower than numpy.core.ma, but > that's a side effect of the flexibility. In the long term, there are some > plans about porting the module to C, but we're talking in quarters more than > in weeks. > > About when it'll be promoted outside the sandbox: well, we need more feedback > from users, as usual. I guess that's the principal stopping block. I'd be > quite grateful if you could try it and let me know what you think. I grew > fond of this child born in pain (explaining to my bosses why I spent so much > time on something which is only remotely connected to what I paid to do...), > so I make sure that the baby behaves... >
I'm inclined to move his masked array over to ma wholesale. The fact that Pierre sees it as his baby is very important to me. If it doesn't have significant compatibility issues than I'm all for it. I'm mainly interested in hearing how people actually using numpy.ma would respond. Perhaps we should move it over and start deprecating numpy.ma?? -Travis > Once again, please don't hesitate to contact me if you have any > comments/complaints/suggestions. > _______________________________________________ > SciPy-user mailing list > [EMAIL PROTECTED] > http://projects.scipy.org/mailman/listinfo/scipy-user > > > _______________________________________________ Numpy-discussion mailing list [email protected] http://projects.scipy.org/mailman/listinfo/numpy-discussion
