On Thu, Jul 18, 2013 at 9:24 PM, Yaroslav Halchenko <[email protected]>wrote:
> > On Thu, 18 Jul 2013, Skipper Seabold wrote: > > > Not sure anyways if my direct numpy.mean application to pandas > DataFrame > > is > > "kosher" -- initially I just assumed that any argument is > asanyarray'ed > > first > > -- but I think here catching TypeError for those incompatible > .mean's > > would not > > hurt either. �What do you think? �Similar logic applies to mean > cousins > > (var, > > std, ...?) decorated around _methods implementations. > > > Related? From a while ago. > > [3]https://github.com/numpy/numpy/pull/160 > > yeah... That is how I thought "it is working", but I guess it was left > without asanyarraying for additional flexibility/performance so any > array-like object could be used, not just ndarray derived classes. > Speaking of which, there is a PR for nan{mean, var, std)<https://github.com/numpy/numpy/pull/3534> that you might want to check before it gets committed. There might be some modifications that you would want to add. Chuck
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
