On 12-Nov-08, at 8:18 PM, David Cournapeau wrote:
On Wed, 2008-11-12 at 19:24 -0500, David Warde-Farley wrote:
Indeed, for the size of problem I *thought* I was running, 32 bit
would be sufficient. In fact I had my data transposed and so was
working with a much larger matrix which would
Hello folks,
I'm doing some rather big matrix products on a G5, and ran into this.
Strangely on the same OS version on my Intel laptop, this isn't an
issue. Available memory isn't the problem either, I don't think, this
machine is pretty beefy.
I'm running the python.org 2.5.2 build of
David Warde-Farley wrote:
Hello folks,
Hi David,
I'm doing some rather big matrix products on a G5, and ran into this.
Strangely on the same OS version on my Intel laptop, this isn't an
issue. Available memory isn't the problem either, I don't think, this
machine is pretty beefy.
Can
On 12-Nov-08, at 6:05 PM, Michael Abshoff wrote:
I'm running the python.org 2.5.2 build of Python, and the latest SVN
build of numpy (though the same thing happened with 1.1.0).
IIRC that is a universal build for 32 bit PPC and Intel, so
depending on
the problem size 32 bits might be
On Wed, 2008-11-12 at 19:24 -0500, David Warde-Farley wrote:
Indeed, for the size of problem I *thought* I was running, 32 bit
would be sufficient. In fact I had my data transposed and so was
working with a much larger matrix which would put me past the 32-bit
bound.
Still, ideally,
