On Mac OS X 10.6.7 with macports python 2.7 I get as follows:
OK (KNOWNFAIL=3, SKIP=1)
Python version:
Python 2.7.1 (r271:86832, Jan 12 2011, 10:44:27)
[GCC 4.2.1 (Apple Inc. build 5664)] on darwin
% gfortran --version
GNU Fortran (GCC) 4.5.3
"Well done" to everyone working on numpy 1.6!
Paul
On Tue, May 3, 2011 at 19:34, Michael Katz wrote:
> Robert, thanks for these quick replies.
>
> So, it sounds like the main thing is for me to get better at thinking
> "declaratively" in terms of these array operations, instead of the
> "imperative" way I normally think about processing arrays in
On 5/3/2011 9:34 PM, Dan Halbert wrote:
> On 5/3/2011 7:52 PM, Gaston Fiore wrote:
>> I'm trying to create a vector (or a matrix, could be either) with
>> 3200975422129 elements but I'm not being successful
> In words, that's about 3.2 trillion float32's, so about 24 trillion
> bytes,> 2^41. So, y
On 5/3/2011 7:52 PM, Gaston Fiore wrote:
> I'm trying to create a vector (or a matrix, could be either) with
> 3200975422129 elements but I'm not being successful
In words, that's about 3.2 trillion float32's, so about 24 trillion
bytes, > 2^41. So, yes, you are running out of memory, by a factor
On Tue, May 3, 2011 at 11:18 AM, Ralf Gommers
wrote:
> I am pleased to announce the availability of the second release
> candidate of NumPy 1.6.0.
nanmin and nanmax are much faster in Numpy 1.6. Plus they now return
an object that has dtype, etc attributes when the input is all NaN.
Broke Bottle
Robert, thanks for these quick replies.
So, it sounds like the main thing is for me to get better at thinking
"declaratively" in terms of these array operations, instead of the "imperative"
way I normally think about processing arrays in C++.
I did look at Numexpr, and that's in the direction I
On Tue, May 3, 2011 at 4:58 PM, Derek Homeier <
de...@astro.physik.uni-goettingen.de> wrote:
> Hi Ralf,
>
> > I am pleased to announce the availability of the second release
> > candidate of NumPy 1.6.0.
> >
> > Compared to the first release candidate, one segfault on (32-bit
> > Windows + MSVC) a
On Tue, May 3, 2011 at 18:58, Michael Katz wrote:
> So I was trying to find a "pure numpy" solution for this. I then learned
> about fancy indexing and boolean indexing, and saw that I could do boolean
> array version:
>
> mapped_colors = np.zeros(unmapped_colors.shape, dtype=np.uint32) + gray
On Tue, May 3, 2011 at 19:03, Benjamin Root wrote:
> I can't comment much on the questions you raise, but I can certainly suggest
> that np.where() function might be a much better choice than some of the
> if-statements.
But it won't be any better than the two fancy-indexing approaches he's used
On Tue, May 3, 2011 at 18:58, Michael Katz wrote:
> I have a basic question about applying functions to array elements. There is
> a rambling introduction here and then I get to the ACTUAL QUESTION about 2/3
> of the way down.
>
> RAMBLING INTRODUCTION
>
> I was trying to do a simple mapping of ar
On Tue, May 3, 2011 at 6:58 PM, Michael Katz wrote:
> I have a basic question about applying functions to array elements. There
> is a rambling introduction here and then I get to the ACTUAL QUESTION about
> 2/3 of the way down.
>
> RAMBLING INTRODUCTION
>
> I was trying to do a simple mapping of
On Tue, May 3, 2011 at 12:07, Matthew Brett wrote:
> Hi,
>
> On Sat, Apr 30, 2011 at 5:21 AM, Ralf Gommers
> wrote:
>> On Wed, Apr 27, 2011 at 8:52 PM, Matthew Brett
>> wrote:
>>> Hi,
>>>
>>> This is just to follow up on a dead thread of mine a little while back.
>>>
>>> I was asking about lett
I have a basic question about applying functions to array elements. There is a
rambling introduction here and then I get to the ACTUAL QUESTION about 2/3 of
the way down.
RAMBLING INTRODUCTION
I was trying to do a simple mapping of array values to other values. So I had:
un
On Tue, May 3, 2011 at 18:45, Keith Goodman wrote:
> On Tue, May 3, 2011 at 11:18 AM, Ralf Gommers
> wrote:
>
>> I am pleased to announce the availability of the second release
>> candidate of NumPy 1.6.0.
>
> I get one failure when I run from ipython but not python. In ipython I
> import a few p
Hello,
I'm trying to create a vector (or a matrix, could be either) with
3200975422129 elements but I'm not being successful, get the following
error:
>>> zeros(width * height, dtype=float32)
Killed
or
>>> zeros((1789127,1789127), dtype=float32)
Killed
I'm assuming that I'm running out of memo
On Tue, May 3, 2011 at 11:18 AM, Ralf Gommers
wrote:
> I am pleased to announce the availability of the second release
> candidate of NumPy 1.6.0.
I get one failure when I run from ipython but not python. In ipython I
import a few packages at startup. One of those packages must be
changing the n
Hi Ralf,
> I am pleased to announce the availability of the second release
> candidate of NumPy 1.6.0.
>
> Compared to the first release candidate, one segfault on (32-bit
> Windows + MSVC) and several memory leaks were fixed. If no new
> problems are reported, the final release will be in one we
On Tue, May 3, 2011 at 5:06 PM, Ralf Gommers
wrote:
> On Tue, May 3, 2011 at 10:35 PM, Christoph Gohlke wrote:
>>
>>
>> On 5/3/2011 11:18 AM, Ralf Gommers wrote:
>>> Hi,
>>>
>>> I am pleased to announce the availability of the second release
>>> candidate of NumPy 1.6.0.
>>>
>>> Compared to the f
I'm seeing these three failures on Solaris 5.10 (x86_64, using Python 2.7.1):
==
FAIL: Test basic arithmetic function errors
--
Traceback (most recent call last):
On Tue, May 3, 2011 at 10:35 PM, Christoph Gohlke wrote:
>
>
> On 5/3/2011 11:18 AM, Ralf Gommers wrote:
>> Hi,
>>
>> I am pleased to announce the availability of the second release
>> candidate of NumPy 1.6.0.
>>
>> Compared to the first release candidate, one segfault on (32-bit
>> Windows + MSV
On 5/3/2011 11:18 AM, Ralf Gommers wrote:
> Hi,
>
> I am pleased to announce the availability of the second release
> candidate of NumPy 1.6.0.
>
> Compared to the first release candidate, one segfault on (32-bit
> Windows + MSVC) and several memory leaks were fixed. If no new
> problems are repo
In article ,
Ralf Gommers wrote:
> Hi,
>
> I am pleased to announce the availability of the second release
> candidate of NumPy 1.6.0.
>...
> Sources and binaries can be found at
> http://sourceforge.net/projects/numpy/files/NumPy/1.6.0rc2/
> For (preliminary) release notes see below.
Thanks!
Hi,
I am pleased to announce the availability of the second release
candidate of NumPy 1.6.0.
Compared to the first release candidate, one segfault on (32-bit
Windows + MSVC) and several memory leaks were fixed. If no new
problems are reported, the final release will be in one week.
Sources and
Hi,
On Sat, Apr 30, 2011 at 5:21 AM, Ralf Gommers
wrote:
> On Wed, Apr 27, 2011 at 8:52 PM, Matthew Brett
> wrote:
>> Hi,
>>
>> This is just to follow up on a dead thread of mine a little while back.
>>
>> I was asking about letters for Clint Whaley's tenure case, from numpy,
>> but I realized
On Mon, May 2, 2011 at 10:55 PM, Mark Wiebe wrote:
> I applied everything, since they're all obviously bugs and the fixes look
> straightforward.
I tested those commits on a few python/OS combinations, all looks
good. So I'll try to tag an RC2 tonight.
Ralf
__
25 matches
Mail list logo
