[Piglit] [PATCH] generated_tests: work around bug in Windows numpy implementation.
Paul Berry
stereotype441 at gmail.com
Fri Sep 9 08:08:20 PDT 2011
On 9 September 2011 06:47, Paul Berry <stereotype441 at gmail.com> wrote:
> Paul,
>>
>> This is not a windows specific bug. It looks like numpy creates many
>> identical type objects on all OSes, so type object identity/equality means
>> nothing.
>>
>> Take for example what "pydoc numpy" outputs on my Linux system:
>>
>> CLASSES
>> __builtin__.object
>> broadcast
>> dtype
>> flatiter
>> generic
>> [...]
>> number
>> [...]
>> integer
>> signedinteger
>> int16
>> int16
>> int32
>> int32
>> int64(signedinteger, __builtin__.int)
>> int64(signedinteger, __builtin__.int)
>> int64(signedinteger, __builtin__.int)
>> int64(signedinteger, __builtin__.int)
>> int64(signedinteger, __builtin__.int)
>> int8
>> int8
>> unsignedinteger
>> uint16
>> uint16
>> uint32
>> uint32
>> uint64
>> uint64
>> uint64
>> uint64
>> uint64
>> uint8
>> uint8
>>
>> You were just lucky on Linux so far, and Windows unlucky, but your luck
>> may change with different numpy versions, and or other systems. Who knows.
>>
>
> Wow. That is enough to convince me that my change is too brittle. Good
> call, Jose.
>
> Do you have any idea if the developers of numpy know about this? It seems
> like a bug to me, and I want to file a bug report, but unfortunately the
> server at projects.scipy.org is giving me errors. I'll try again later
> today.
>
Ok, bug report filed, if anyone is curious to follow along:
http://projects.scipy.org/numpy/ticket/1950
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/piglit/attachments/20110909/6f9d4e07/attachment-0001.htm>
More information about the Piglit
mailing list