Hi Matt,
On Wed, Sep 12, 2012 at 1:27 PM, Travis Oliphant wrote:
Is this intended? Is there a performance reason to keep the same
strides in 1.7.0?
>>>
>>> I believe that this could be because in 1.7.0, NumPy was changed so that
>>> copying does not always default to "C-order" bu
>>>
>>> Is this intended? Is there a performance reason to keep the same
>>> strides in 1.7.0?
>>
>> I believe that this could be because in 1.7.0, NumPy was changed so that
>> copying does not always default to "C-order" but to "Keep-order".So, in
>> 1.7.0, the strides of b is governed by
Hi,
On Wed, Sep 12, 2012 at 7:58 PM, Travis Oliphant wrote:
>
> On Sep 12, 2012, at 1:36 PM, Matthew Brett wrote:
>
>> Hi,
>>
>> We hit a subtle behavior change for the ``astype`` array method
>> between 1.6.1 and 1.7.0 beta.
>>
>> In 1.6.1:
>>
>>
>> In [18]: a = np.arange(24).reshape((2, 3, 4)).
On Sep 12, 2012, at 1:36 PM, Matthew Brett wrote:
> Hi,
>
> We hit a subtle behavior change for the ``astype`` array method
> between 1.6.1 and 1.7.0 beta.
>
> In 1.6.1:
>
>
> In [18]: a = np.arange(24).reshape((2, 3, 4)).transpose((1, 2, 0))
>
> In [19]: a.flags
> Out[19]:
> C_CONTIGUOUS :
Hi,
We hit a subtle behavior change for the ``astype`` array method
between 1.6.1 and 1.7.0 beta.
In 1.6.1:
In [18]: a = np.arange(24).reshape((2, 3, 4)).transpose((1, 2, 0))
In [19]: a.flags
Out[19]:
C_CONTIGUOUS : False
F_CONTIGUOUS : False
OWNDATA : False
WRITEABLE : True
ALIGNED
On Wed, Sep 12, 2012 at 2:46 PM, Matthew Brett wrote:
> Hi,
>
> I just noticed that this works for numpy 1.6.1:
>
> In [36]: np.concatenate(([2, 3], [1]), 1)
> Out[36]: array([2, 3, 1])
>
> but the beta release branch:
>
> In [3]: np.concatenate(([2, 3], [1]), 1)
>
Hi,
I just noticed that this works for numpy 1.6.1:
In [36]: np.concatenate(([2, 3], [1]), 1)
Out[36]: array([2, 3, 1])
but the beta release branch:
In [3]: np.concatenate(([2, 3], [1]), 1)
---
IndexError
