Dylan,
The error appears to be in example.c, not example_wrap.c. The way you have
written it, I think it should be double **x0.
But the SWIG typemaps require double*.
You could write it with double *x0, but then index with x0[i*m+j].
Or, if you want the [i][j] indexing, you could write a wrap
The framework for catching errors relies on hardware flags getting set and our
C code making the right calls to detect those flags.
This has usually worked correctly in the past --- but it is an area where
changes in compilers or platforms could create problems.
We should test to be sure that
On Tue, Sep 4, 2012 at 8:38 PM, Travis Oliphant wrote:
>
> There is an error context that controls how floating point signals are
> handled. There is a separate control for underflow, overflow, divide by
> zero, and invalid. IIRC, it was decided on this list a while ago to make
> the defaul
There is an error context that controls how floating point signals are handled.
There is a separate control for underflow, overflow, divide by zero, and
invalid. IIRC, it was decided on this list a while ago to make the default
ignore for underflow and warning for overflow, invalid and div
Hi,
When running the test suite, there are problems of this kind:
https://github.com/numpy/numpy/issues/394
which then causes for example the Debian buildbots tests to fail
(https://github.com/numpy/numpy/issues/406).
The problem is really simple:
>>> from numpy import array, abs, nan
>>> a =
Hello,
I am trying to use numpy.i to move a function from python to C that takes a
2-D array as an input and am having difficulty. The code is pretty long so
I've made a simple example that recreates the error.
example.c:
#include
#include "example.h"
void matrix_example (int n, int m, double
On Sat, Sep 1, 2012 at 2:19 AM, Sandro Tosi wrote:
> On Fri, Aug 31, 2012 at 8:07 PM, Sandro Tosi wrote:
>> On Fri, Aug 31, 2012 at 7:17 PM, Ondřej Čertík
>> wrote:
>>> If you could create issues at github: https://github.com/numpy/numpy/issues
>>> that would be great. If you have time, also wi
On Tue, Sep 4, 2012 at 2:58 PM, wrote:
> On Tue, Sep 4, 2012 at 5:49 PM, Ondřej Čertík wrote:
>> On Tue, Sep 4, 2012 at 1:48 PM, wrote:
>>> On Tue, Sep 4, 2012 at 4:37 PM, Nathaniel Smith wrote:
On Tue, Sep 4, 2012 at 9:17 PM, Ondřej Čertík
wrote:
> On Tue, Sep 4, 2012 at 12:4
On Tue, Sep 4, 2012 at 5:49 PM, Ondřej Čertík wrote:
> On Tue, Sep 4, 2012 at 1:48 PM, wrote:
>> On Tue, Sep 4, 2012 at 4:37 PM, Nathaniel Smith wrote:
>>> On Tue, Sep 4, 2012 at 9:17 PM, Ondřej Čertík
>>> wrote:
On Tue, Sep 4, 2012 at 12:41 PM, Ondřej Čertík
wrote:
> On Tue,
On Tue, Sep 4, 2012 at 1:48 PM, wrote:
> On Tue, Sep 4, 2012 at 4:37 PM, Nathaniel Smith wrote:
>> On Tue, Sep 4, 2012 at 9:17 PM, Ondřej Čertík
>> wrote:
>>> On Tue, Sep 4, 2012 at 12:41 PM, Ondřej Čertík
>>> wrote:
On Tue, Sep 4, 2012 at 12:31 PM, Ondřej Čertík
wrote:
> On
On Tue, Sep 4, 2012 at 2:37 PM, Nathaniel Smith wrote:
> On Tue, Sep 4, 2012 at 9:17 PM, Ondřej Čertík
> wrote:
> > On Tue, Sep 4, 2012 at 12:41 PM, Ondřej Čertík
> wrote:
> >> On Tue, Sep 4, 2012 at 12:31 PM, Ondřej Čertík
> wrote:
> >>> On Tue, Sep 4, 2012 at 3:15 AM, Nathaniel Smith wrote:
On Tue, Sep 4, 2012 at 4:37 PM, Nathaniel Smith wrote:
> On Tue, Sep 4, 2012 at 9:17 PM, Ondřej Čertík wrote:
>> On Tue, Sep 4, 2012 at 12:41 PM, Ondřej Čertík
>> wrote:
>>> On Tue, Sep 4, 2012 at 12:31 PM, Ondřej Čertík
>>> wrote:
On Tue, Sep 4, 2012 at 3:15 AM, Nathaniel Smith wrote:
On Tue, Sep 4, 2012 at 9:17 PM, Ondřej Čertík wrote:
> On Tue, Sep 4, 2012 at 12:41 PM, Ondřej Čertík
> wrote:
>> On Tue, Sep 4, 2012 at 12:31 PM, Ondřej Čertík
>> wrote:
>>> On Tue, Sep 4, 2012 at 3:15 AM, Nathaniel Smith wrote:
The last two Travis builds of master have failed consisten
On Tue, Sep 4, 2012 at 12:41 PM, Ondřej Čertík wrote:
> On Tue, Sep 4, 2012 at 12:31 PM, Ondřej Čertík
> wrote:
>> On Tue, Sep 4, 2012 at 3:15 AM, Nathaniel Smith wrote:
>>> The last two Travis builds of master have failed consistently with the
>>> same error:
>>> http://travis-ci.org/#!/nump
On Tue, Sep 4, 2012 at 12:31 PM, Ondřej Čertík wrote:
> On Tue, Sep 4, 2012 at 3:15 AM, Nathaniel Smith wrote:
>> The last two Travis builds of master have failed consistently with the
>> same error:
>> http://travis-ci.org/#!/numpy/numpy/builds
>> It looks like a real failure -- we're getting
On Tue, Sep 4, 2012 at 3:15 AM, Nathaniel Smith wrote:
> The last two Travis builds of master have failed consistently with the
> same error:
> http://travis-ci.org/#!/numpy/numpy/builds
> It looks like a real failure -- we're getting the same error on every
> build variant, some sort of problem
Hi,
On Tue, Sep 4, 2012 at 2:18 PM, Nathaniel Smith wrote:
> On Tue, Sep 4, 2012 at 1:47 PM, Scott Sinclair
> wrote:
>> On 4 September 2012 12:23, Matthew Brett wrote:
>>> On Tue, Sep 4, 2012 at 11:15 AM, Nathaniel Smith wrote:
The last two Travis builds of master have failed consistently
On Tue, Sep 4, 2012 at 1:47 PM, Scott Sinclair
wrote:
> On 4 September 2012 12:23, Matthew Brett wrote:
>> On Tue, Sep 4, 2012 at 11:15 AM, Nathaniel Smith wrote:
>>> The last two Travis builds of master have failed consistently with the
>>> same error:
>>> http://travis-ci.org/#!/numpy/numpy/
On 4 September 2012 12:23, Matthew Brett wrote:
> On Tue, Sep 4, 2012 at 11:15 AM, Nathaniel Smith wrote:
>> The last two Travis builds of master have failed consistently with the
>> same error:
>> http://travis-ci.org/#!/numpy/numpy/builds
>> It looks like a real failure -- we're getting the s
Hi,
On Tue, Sep 4, 2012 at 11:15 AM, Nathaniel Smith wrote:
> The last two Travis builds of master have failed consistently with the
> same error:
> http://travis-ci.org/#!/numpy/numpy/builds
> It looks like a real failure -- we're getting the same error on every
> build variant, some sort of p
The last two Travis builds of master have failed consistently with the
same error:
http://travis-ci.org/#!/numpy/numpy/builds
It looks like a real failure -- we're getting the same error on every
build variant, some sort of problem in test_pareto. Example:
http://travis-ci.org/#!/numpy/numpy/jo
21 matches
Mail list logo
