On Thu, Oct 8, 2009 at 9:25 PM, Travis Oliphant wrote:
>
> On Oct 8, 2009, at 7:19 AM, Travis Oliphant wrote:
>
>>
>> I just checked a fix for this into SVN (tests still need to be added
>> though...)
>>
>> I can't currently build SVN on my Mac for some reason (I don't know if
>> it has to do with
On Oct 8, 2009, at 12:08 PM, Michael Droettboom wrote:
Thanks! I guess I won't file a bug then ;)
Probably still should, actually: Until the tests get committed, the
bug is not really "fixed"
-Travis
___
NumPy-Discussion mailing list
NumPy-
Thanks! I guess I won't file a bug then ;)
Mike
Travis Oliphant wrote:
> On Oct 7, 2009, at 10:28 AM, Michael Droettboom wrote:
>
>
>> I'm noticing an inconsistency as to how complex numbers are
>> byteswapped
>> as arrays vs. scalars, and wondering if I'm doing something wrong.
>>
>>
On Oct 8, 2009, at 7:19 AM, Travis Oliphant wrote:
>
> I just checked a fix for this into SVN (tests still need to be added
> though...)
>
> I can't currently build SVN on my Mac for some reason (I don't know if
> it has to do with recent changes or not, but I don't have time to
> track it down r
On Oct 7, 2009, at 10:28 AM, Michael Droettboom wrote:
> I'm noticing an inconsistency as to how complex numbers are
> byteswapped
> as arrays vs. scalars, and wondering if I'm doing something wrong.
>
x = np.array([-1j], '>>> x.tostring().encode('hex')
> '80bf'
> # This is a l
On Oct 7, 2009, at 10:28 AM, Michael Droettboom wrote:
> I'm noticing an inconsistency as to how complex numbers are
> byteswapped
> as arrays vs. scalars, and wondering if I'm doing something wrong.
>
x = np.array([-1j], '>>> x.tostring().encode('hex')
> '80bf'
> # This is a l
I'm noticing an inconsistency as to how complex numbers are byteswapped
as arrays vs. scalars, and wondering if I'm doing something wrong.
>>> x = np.array([-1j], '>> x.tostring().encode('hex')
'80bf'
# This is a little-endian representation, in the order (real, imag)
# When I swap
