[Numpy-discussion] Numpy 1.3.0 rc1 fails find_duplicates on Solaris

Pauli Virtanen pav@iki...
Mon Mar 30 16:12:35 CDT 2009


Mon, 30 Mar 2009 14:03:17 -0600, Charles R Harris wrote:

> On Mon, Mar 30, 2009 at 10:28 AM, Mark Sienkiewicz
> <sienkiew@stsci.edu>wrote:
> 
>> Numpy 1.3.0 rc1 fails this self-test on Solaris.
[clip]
>> ======================================================================
>> FAIL: Test find_duplicates
>> ----------------------------------------------------------------------
>>         assert_equal(test[0], a[control])
>>
>>  x: array([(1, (2.0, 'B')), (2, (2.0, 'B')), (2, (2.0, 'B')), (1, (2.0,
>> 'B'))],
>>      dtype=[('A', '>i4'), ('B', [('BA', '>f8'), ('BB', '|S1')])])
>>  y: array([(2, (2.0, 'B')), (1, (2.0, 'B')), (2, (2.0, 'B')), (1, (2.0,
>> 'B'))],
>>      dtype=[('A', '>i4'), ('B', [('BA', '>f8'), ('BB', '|S1')])])
>
> These are new (two months old) tests. Hmm, they are also marked as known
> failures on win32. I wonder why they fail there and not on linux? I
> think you should open a ticket for this.

The data seems to be in a different order in the index array and in the 
data array returned by `find_duplicates`.

It is intended that find_duplicates guarantees that the returned indices 
correspond to the returned values?

Another question: the 'recfunctions' is not imported anywhere in numpy?

(BTW, it might be good not to keep commented-out code such as those 
np.knownfail decorators in the repository, unless it's explained why it's 
commented out...)

-- 
Pauli Virtanen



More information about the Numpy-discussion mailing list