On Fri, Mar 21, 2014 at 6:49 PM, <[email protected]> wrote: > > > > On Fri, Mar 21, 2014 at 8:46 PM, Charles R Harris < > [email protected]> wrote: > >> >> >> >> On Fri, Mar 21, 2014 at 6:26 PM, Alan G Isaac <[email protected]>wrote: >> >>> The documentation of numpy.unique >>> http://docs.scipy.org/doc/numpy/reference/generated/numpy.unique.html >>> does not seem to promise that return_index=True will always index the >>> *first* occurrence of each unique item, which I believe is the current >>> behavior. >>> >>> A promise would be nice. >>> Is it intended? >>> >>> >> Yes, it is intended, although the required mergesort wasn't available for >> all types before numpy 1.7. >> > > Does this mean return_inverse works again for all cases, even with > return_index? > > I removed return_index from my code in statsmodels because I make frequent > use of return_inverse, which was broken. We don't have any unittests in > statsmodels anymore that use both return_xxx. > > I don't know, needs checking. Seems to work now with a simple trial array of integers.
Chuck
_______________________________________________ NumPy-Discussion mailing list [email protected] http://mail.scipy.org/mailman/listinfo/numpy-discussion
