Re: [Numpy-discussion] ANN: 1.8.0b2 release.

2013-09-11 Thread Frédéric Bastien
Hi, I create an Ubuntu VM, cloned numpy and it compiled correctly in it. I tried in my normal development environment (instead of a virtualenv) with my old clone that is updated of numpy and it failed. So this isn't virtualenv. I created a new clone of numpy and it compiled correctly with my nor

Re: [Numpy-discussion] fast_any_all , a trivial but fast/useful helper function for numpy

2013-09-11 Thread Graeme B. Bell
>From my previous mail: >> this has the same performance as your code: >> a = empty([3] list(A.shape) For anyone that is interested. I ran a benchmark on the code after Julian kindly provided me with a correction to the listing he posted. >> a = empty([3] + list(A.shape)) >> a[0] = A>5; a[1] =

Re: [Numpy-discussion] strange behaviour with numpy arrays

2013-09-11 Thread Julian Taylor
On 11.09.2013 12:33, antlarac wrote: > Hi, I have a numpy array, and I want to create another variable equal to it, > to back it up for later calculations, because the first array will change. > But after the first array changes, the second automatically changes to the > same value. An example of w

[Numpy-discussion] strange behaviour with numpy arrays

2013-09-11 Thread antlarac
Hi, I have a numpy array, and I want to create another variable equal to it, to back it up for later calculations, because the first array will change. But after the first array changes, the second automatically changes to the same value. An example of what happens: import numpy as np a=np.zeros((