On Tue, Dec 4, 2012 at 8:14 AM, Ondřej Čertík wrote:
> On Mon, Dec 3, 2012 at 7:10 PM, Nathaniel Smith wrote:
>> On 4 Dec 2012 02:27, "Ondřej Čertík" wrote:
>>>
>>> Hi,
>>>
>>> I started to work on the release again and noticed weird failures at
>>> Travis-CI:
>> […]
>>> File
>>> "/home/travis
Hi,
maybe someone has an opinion about how this can be handled and was not
yet aware of this.
In current numpy master (probably being reverted), the definition for
contiguous arrays is changed such that it means "Contiguous in memory"
and nothing more. What this means is this:
1. An array of siz
On Mon, Dec 3, 2012 at 7:10 PM, Nathaniel Smith wrote:
> On 4 Dec 2012 02:27, "Ondřej Čertík" wrote:
>>
>> Hi,
>>
>> I started to work on the release again and noticed weird failures at
>> Travis-CI:
> […]
>> File
>> "/home/travis/virtualenv/python2.5/lib/python2.5/site-packages/numpy/core/test
On Tue, Dec 4, 2012 at 8:57 AM, Sebastian Berg
wrote:
> Hey,
>
> Maybe someone has an opinion about this (since in fact it is new
> behavior, so it is undefined). `np.take` used to not allow 0-d/scalar
> input but did allow any other dimensions for the indices. Thinking about
> changing this, mean
Hey,
Maybe someone has an opinion about this (since in fact it is new
behavior, so it is undefined). `np.take` used to not allow 0-d/scalar
input but did allow any other dimensions for the indices. Thinking about
changing this, meaning that:
np.take(np.arange(5), 0)
works. I was wondering if an
