Hi Neil,
Neil Crighton wrote:
>>> What about merging unique and unique1d? They're essentially identical for
>>> an
>>> array input, but unique uses the builtin set() for non-array inputs and so
>>> is
>>> around 2x faster in this case - see below. Is it worth accepting a speed
>>> regression fo
> > What about merging unique and unique1d? They're essentially identical for
> > an
> > array input, but unique uses the builtin set() for non-array inputs and so
> > is
> > around 2x faster in this case - see below. Is it worth accepting a speed
> > regression for unique to get rid of the func
Neil Crighton wrote:
> Robert Cimrman ntc.zcu.cz> writes:
>
>> Hi,
>>
>> I am starting a new thread, so that it reaches the interested people.
>> Let us discuss improvements to arraysetops (array set operations) at [1]
>> (allowing non-unique arrays as function arguments, better naming
>> conve
Robert Cimrman ntc.zcu.cz> writes:
>
> Hi,
>
> I am starting a new thread, so that it reaches the interested people.
> Let us discuss improvements to arraysetops (array set operations) at [1]
> (allowing non-unique arrays as function arguments, better naming
> conventions and documentation).
Hi,
I am starting a new thread, so that it reaches the interested people.
Let us discuss improvements to arraysetops (array set operations) at [1]
(allowing non-unique arrays as function arguments, better naming
conventions and documentation).
r.
[1] http://projects.scipy.org/numpy/ticket/1133
