Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: Neil Crighton <neilcrighton <at> gmail.com>
Subject: Deprecating function_base.unique()
Newsgroups: gmane.comp.python.numeric.general
Date: Monday 29th June 2009 21:49:47 UTC (over 8 years ago)
Hi,

There was some discussion (e.g.
http://article.gmane.org/gmane.comp.python.numeric.general/30629)
about changes to the arraysetops module to consolidate the separate
unique/non-unique functions and rename setmember1d to in1d. There's a
patch that makes these changes in ticket 1133
(http://projects.scipy.org/numpy/ticket/1133)

The patch also deprecates function_base.unique and renames
arraysetops.unique1d to arraysetops.unique as per this discussion:
http://article.gmane.org/gmane.comp.python.numeric.general/31068

Is deprecating function_base.unique the right thing to do?
Alternatively, we could deprecate unique1d and transfer its
functionality to function_base.unique, but since many of the setops
functions use unique, arraysetops seems a more natural place for it.

Does anyone have any thoughts about this?

Neil
 
CD: 50ms