On Thu, Jun 28, 2012 at 8:06 PM, Nathaniel Smith wrote:
> On Thu, Jun 28, 2012 at 7:13 AM, Pierre Haessig
> wrote:
>> Hi Nathaniel,
>> Le 27/06/2012 20:22, Nathaniel Smith a écrit :
>>> According to the Travis-CI build logs, this code produces
>>> non-deterministic behaviour in master:
>> You mea
On Thu, Jun 28, 2012 at 7:13 AM, Pierre Haessig
wrote:
> Hi Nathaniel,
> Le 27/06/2012 20:22, Nathaniel Smith a écrit :
>> According to the Travis-CI build logs, this code produces
>> non-deterministic behaviour in master:
> You mean non-deterministic across different builds, not across different
Hi Nathaniel,
Le 27/06/2012 20:22, Nathaniel Smith a écrit :
> According to the Travis-CI build logs, this code produces
> non-deterministic behaviour in master:
You mean non-deterministic across different builds, not across different
executions on the same build, right ?
I just ran a small loop :
Hi Nathaniel,
On Wed, Jun 27, 2012 at 11:22 AM, Nathaniel Smith wrote:
> According to the Travis-CI build logs, this code produces
> non-deterministic behaviour in master:
>
> a = np.arange(5)
> a[:3] = a[2:]
> assert_equal(a, [2, 3, 4, 3, 4])
>
> Sometimes 'a' is [2, 3, 4, 3, 4], and sometime
According to the Travis-CI build logs, this code produces
non-deterministic behaviour in master:
a = np.arange(5)
a[:3] = a[2:]
assert_equal(a, [2, 3, 4, 3, 4])
Sometimes 'a' is [2, 3, 4, 3, 4], and sometimes it is [4, 3, 4, 3, 4].
The latter is what you get if the assignment is done 'backw
