Re: [Numpy-discussion] how is y += x computed when y.strides = (0, 8) and x.strides=(16, 8) ?

2012-09-05 Thread Sebastian Berg
Hey, No idea if this is simply not support or just a bug, though I am guessing that such usage simply is not planned. However, this also has to do with buffering, so unless the behaviour is substantially changed, I would not expect even predictable results. I have used things like a[1:] += a[:-1]

Re: [Numpy-discussion] how is y += x computed when y.strides = (0, 8) and x.strides=(16, 8) ?

2012-09-05 Thread Friedrich Romstedt
Poor Sebastian, you make the mistake of asking difficult questions. I noticed that it should be [6, 10] not [6, 12], and in fact is with numpy-1.4.1; while I observe the [4, 6] result with numpy-1.6.1. Logs follow: numpy-1.4.1 in Python-2.6.5 on Mac (intel 64bit) with Python + numpy built from

Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-05 Thread Ondřej Čertík
Hi Fred, On Wed, Sep 5, 2012 at 10:56 AM, Nathaniel Smith wrote: > 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 a function,

Re: [Numpy-discussion] FWIW: "regressions" of dependees of nukmpy 1.7.0b1

2012-09-05 Thread Yaroslav Halchenko
On Wed, 05 Sep 2012, Nathaniel Smith wrote: > It is an intentional change: > https://github.com/numpy/numpy/commit/b7cc20ad#L5R77 > but the benefits aren't necessarily *that* compelling, so it could > certainly be revisited if there are unforeseen downsides. (Mostly it > means that intermediate

Re: [Numpy-discussion] FWIW: "regressions" of dependees of nukmpy 1.7.0b1

2012-09-05 Thread Nathaniel Smith
On Wed, Sep 5, 2012 at 10:02 PM, Yaroslav Halchenko wrote: > quick question -- either this is a desired effect that ndarray.base is no > longer chains to point to all parent arrays? following code produces > different outputs with 1.6.3 and 1.7.0b1: > > $> python -c 'import numpy as np; print np._

Re: [Numpy-discussion] FWIW: "regressions" of dependees of numpy 1.7.0b1

2012-09-05 Thread Yaroslav Halchenko
and another, quite weird one -- initially it was crashing with the same error on np.dot(Vh.T, U.T) but while adding print statements to troubleshoot it, started to fail on print: File "/home/yoh/proj/pymvpa/pymvpa/mvpa2/mappers/procrustean.py", line 164, in _train print "Vh:", Vh File

Re: [Numpy-discussion] FWIW: "regressions" of dependees of nukmpy 1.7.0b1

2012-09-05 Thread Yaroslav Halchenko
quick question -- either this is a desired effect that ndarray.base is no longer chains to point to all parent arrays? following code produces different outputs with 1.6.3 and 1.7.0b1: $> python -c 'import numpy as np; print np.__version__; a=np.arange(10); print a[:4].base is a, a[:4][:3].base i

[Numpy-discussion] FWIW: "regressions" of dependees of nukmpy 1.7.0b1

2012-09-05 Thread Yaroslav Halchenko
Recently Sandro uploaded 1.7.0b1 into Debian experimental so I decided to see if this bleeding edge version doesn't break some of its dependees... Below is a copy of http://www.onerussian.com/Linux/deb/logs/python-numpy_1.7.0~b1-1_amd64.testrdepends.debian-sid/python-numpy_1.7.0~b1-1_amd64.testrde

Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-05 Thread David Cournapeau
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 a function, not just small code change. > > The problem is that we can'

Re: [Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-05 Thread Nathaniel Smith
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 a function, not just small code change. My understanding was that 1.7 is not suppose

Re: [Numpy-discussion] encounter error while it's testing

2012-09-05 Thread David Cournapeau
On Wed, Sep 5, 2012 at 8:50 AM, 心如烛光 <275438...@qq.com> wrote: > Hi,everybody. > I have installed scipy with commend:"pip install scipy" (OSX lion > 10.7.4) > But I encounter error while testing.BTW,the test of numpy is OK. gcc-llvm (the default gcc) is known to not work with scipy. It may

[Numpy-discussion] Numpy 1.7b1 API change cause big trouble

2012-09-05 Thread Frédéric Bastien
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 a function, not just small code change. The problem is that we can't access fields from PyArrayObject anymore, we absolutely must use the old macro/ne

[Numpy-discussion] problem with scipy's test

2012-09-05 Thread ????????
Hi,every body. I encounter the error while the scipy is testing . I wanna know why and how to fix it.(OSX lion 10.7.4) here is part of the respond: AssertionError: Not equal to tolerance rtol=4.44089e-13, atol=4.44089e-13 error for eigsh:general, typ=d, which=SA, sigma=0.5, mattype=a

[Numpy-discussion] encounter error while it's testing

2012-09-05 Thread ????????
Hi,everybody. I have installed scipy with commend:"pip install scipy" (OSX lion 10.7.4) But I encounter error while testing.BTW,the test of numpy is OK. I input: >>> import scipy >>> scipy.test() And this is the respond: Running unit tests for scipy NumPy version 1.8.0.de