[Numpy-discussion] ANN: NumPy 1.6.1 release candidate 2

[Bruce Southey]

On Wed, Jul 6, 2011 at 1:56 PM, Christoph Gohlke <cgohlke at uci.edu> wrote:
>
>
> On 7/6/2011 10:57 AM, Russell E. Owen wrote:
>> In article
>> <CABL7CQhNnjkzK9XNrLVDArSdKNwRM4eV0mXdUrJSaXq73EbwcQ at mail.gmail.com>,
>>   Ralf Gommers<ralf.gommers at googlemail.com>  wrote:
>>
>>> On Tue, Jul 5, 2011 at 11:41 PM, Russell E. Owen<rowen at uw.edu>  wrote:
>>>
>>>> In article<BANLkTi=LXiTcrv1LgMtP=p9nF8eMr8=+hw at mail.gmail.com>,
>>>>   Ralf Gommers<ralf.gommers at googlemail.com>  wrote:
>>>>
>>>>> https://sourceforge.net/projects/numpy/files/NumPy/1.6.1rc2/
>>>>
>>>> Will there be a Mac binary for 32-bit pythons (one that is compatible
>>>> with older versions of MacOS X)? At present I only see a 64-bit
>>>> 10.6-only version.
>>>>
>>>>
>>>> Yes there will be for the final release (10.4-10.6 compatible). I can't
>>> create those on my own computer, so sometimes I don't make them for RCs.
>>
>> I'm glad they will be present for the final release.
>>
>> FYI: I built my own 1.6.1rc2 against Python 2.7.2 (the 32-bit Mac
>> version from python.org). I reproduced a memory error that I've been
>> trying to narrow down. This is ticket 1896:
>> <http://projects.scipy.org/numpy/ticket/1896>
>> and the problem is also in 1.6.0.
>>
>> -- Russell
>>
>
>
> I can reproduce this error on Windows. It looks like a serious regression.
>
> Christoph
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
I do get this error in the code without tinker on the first loop.

I did notice that the original array (dataArr) is float64 but the
second array (scaledArr) is only float32. The problem is removed by
changing the dtype of scaledArr to float64. Thus, it would appear some
memory allocation related error to squeeze a float64 result into a
memory allocated for a float32 array.

Bruce