preamble: the bug here seems to be due to incorrect
np.asarray(ctypes.cdouble array)
ok -- I tried with a debug build of python and -O0 build of numpy, and
the same old valgrind... this time valgrind is silent BUT then python itself
says
test_simple (mvpa2.tests.test_procrust.Procru
Hi,
On Wed, Sep 5, 2012 at 7:05 PM, David Cournapeau wrote:
> Hi Frederic,
>
> On Wed, Sep 5, 2012 at 6:36 PM, Frédéric Bastien wrote:
>> Hi,
>>
>> I spent up to now 2 or 3 days making change to Theano to support numpy
>> 1.7b1. But now, I just find an interface change that will need
>> recoding
On Thu, Sep 6, 2012 at 10:07 AM, Frédéric Bastien wrote:
> Hi,
>
> I reply with more information probably later today or tomorrow, but I
> think i need to finish everything to give you the exact information.
>
> Part of the problem I had was that by default there is a warning that
> is generated.
On Thu, 06 Sep 2012, Aron Ahmadia wrote:
>Are you running the valgrind test with the Python suppression
>
> file:�[1]http://svn.python.org/projects/python/trunk/Misc/valgrind-python.supp
yes -- on Debian there is /usr/lib/valgrind/python.supp which comes
with python package and I belie
Hi,
I reply with more information probably later today or tomorrow, but I
think i need to finish everything to give you the exact information.
Part of the problem I had was that by default there is a warning that
is generated. It tell that to remove this warning we need to set
NPY_NO_DEPRECATED_A
Are you running the valgrind test with the Python suppression file:
http://svn.python.org/projects/python/trunk/Misc/valgrind-python.supp ?
Cheers,
A
On Wed, Sep 5, 2012 at 10:14 PM, Yaroslav Halchenko wrote:
> and another, quite weird one -- initially it was crashing with the same
> error on
>
On Wed, Sep 5, 2012 at 1:38 PM, Yaroslav Halchenko wrote:
> skimage_0.6.1-1.dscok FAILED
This breakage is due to
https://github.com/numpy/numpy/issues/392
Thanks for checking!
Stéfan
___
NumPy-Discussion mailing list
Num
On Thu, Sep 6, 2012 at 1:41 AM, Sebastian Berg
wrote:
> Hey,
>
> No idea if this is simply not support or just a bug, though I am
> guessing that such usage simply is not planned.
I think that's right... currently numpy simply makes no guarantees
about what order ufunc loops will be performed in,
