Matthew Brett :
> Hi,
>
> On Mon, Nov 8, 2010 at 10:34 AM, Pauli Virtanen wrote:
>
>> Mon, 08 Nov 2010 19:31:31 +0100, Pauli Virtanen wrote:
>>
>>
>>> ma, 2010-11-08 kello 18:56 +0100, LittleBigBrain kirjoitti:
>>>
In my system '<' is the native byte-order, but unless I change
Hi,
On Mon, Nov 8, 2010 at 10:34 AM, Pauli Virtanen wrote:
> Mon, 08 Nov 2010 19:31:31 +0100, Pauli Virtanen wrote:
>
>> ma, 2010-11-08 kello 18:56 +0100, LittleBigBrain kirjoitti:
>>> In my system '<' is the native byte-order, but unless I change the
>>> byte-order label to '=', it won't work in
Mon, 08 Nov 2010 19:31:31 +0100, Pauli Virtanen wrote:
> ma, 2010-11-08 kello 18:56 +0100, LittleBigBrain kirjoitti:
>> In my system '<' is the native byte-order, but unless I change the
>> byte-order label to '=', it won't work in linalg sub-module, but in
>> others works OK. I am not sure whethe
ma, 2010-11-08 kello 18:56 +0100, LittleBigBrain kirjoitti:
> In my system '<' is the native byte-order, but unless I change the
> byte-order label to '=', it won't work in linalg sub-module, but in
> others works OK. I am not sure whether this is an expected behavior or
> a bug?
> >>> import sys
>
Hi everyone,
In my system '<' is the native byte-order, but unless I change the
byte-order label to '=', it won't work in linalg sub-module, but in
others works OK. I am not sure whether this is an expected behavior or
a bug?
>>> import sys
>>> sys.byteorder
'little'
>>> a.dtype.byteorder
'<'
>>> b
