On 16 Nov 2007, at 1:46 AM, Michael McNeil Forbes wrote:
On 15 Nov 2007, at 8:23 PM, David Cournapeau wrote:
Could you try without atlas ? Also, how did you configure atlas when
building it ? It seems that atlas is definitely part of the problem
(everybody having the problem does use atlas),
On 15 Nov 2007, at 8:23 PM, David Cournapeau wrote:
Could you try without atlas ? Also, how did you configure atlas when
building it ? It seems that atlas is definitely part of the problem
(everybody having the problem does use atlas), and that it involves
Core
2 duo.
David
It seems to
Michael McNeil Forbes wrote:
On 13 Nov 2007, at 9:43 AM, Geoffrey Zhu wrote:
On Nov 13, 2007 2:37 AM, David Cournapeau [EMAIL PROTECTED]
u.ac.jp wrote:
Geoffrey Zhu wrote:
Pointer problems are usually random...
...
The original MSI version hangs on
On 15 Nov 2007, at 2:45 AM, David Cournapeau wrote:
Which fortran compiler are you using ?
GNU Fortran (GCC) 3.4.6 20060404
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
On 13 Nov 2007, at 9:43 AM, Geoffrey Zhu wrote:
On Nov 13, 2007 2:37 AM, David Cournapeau [EMAIL PROTECTED]
u.ac.jp wrote:
Geoffrey Zhu wrote:
Pointer problems are usually random...
...
The original MSI version hangs on numpy.test() if I open IDLE and type
import numpy
numpy.test()
If I
Michael McNeil Forbes wrote:
On 13 Nov 2007, at 9:43 AM, Geoffrey Zhu wrote:
On Nov 13, 2007 2:37 AM, David Cournapeau [EMAIL PROTECTED]
u.ac.jp wrote:
Geoffrey Zhu wrote:
Pointer problems are usually random...
...
The original MSI version hangs on
I have also been having random problems with the latest numpy from
svn built on an Intel core 2 Duo Linux box running in 64 bit mode
under Red Hat 3.4.6-8 with the gcc 3.4.6 20060404 and ATLAS 3.8.0.
Could you try without atlas ? Also, how did you configure atlas when
building it ? It seems
On Nov 13, 2007 8:42 PM, David Cournapeau [EMAIL PROTECTED] wrote:
Keith Goodman wrote:
On Nov 12, 2007 10:51 AM, David Cournapeau [EMAIL PROTECTED] wrote:
On Nov 13, 2007 3:37 AM, Keith Goodman [EMAIL PROTECTED] wrote:
On Nov 12, 2007 10:10 AM, Peter Creasey [EMAIL PROTECTED] wrote:
Keith Goodman wrote:
On Nov 13, 2007 8:42 PM, David Cournapeau [EMAIL PROTECTED] wrote:
Here we are:
http://www.ar.media.kyoto-u.ac.jp/members/david/archives/numpy-1.0.4.win32-py2.4.exe
Thank you. He said it worked. He didn't even notice a slow down
without ATLAS. On some calculations the
Geoffrey Zhu wrote:
Yes, with the MSI I can always reproduce the problem with
numpy.test(). It always hangs.With the egg it does not hang. Pointer
problems are usually random, but not random if we are using the same
binaries in EGG and MSI and variables are always initialized to
certain
Yes, with the MSI I can always reproduce the problem with
numpy.test(). It always hangs.With the egg it does not hang. Pointer
problems are usually random, but not random if we are using the same
binaries in EGG and MSI and variables are always initialized to
certain value.
I can
On Nov 12, 2007 10:51 AM, David Cournapeau [EMAIL PROTECTED] wrote:
On Nov 13, 2007 3:37 AM, Keith Goodman [EMAIL PROTECTED] wrote:
On Nov 12, 2007 10:10 AM, Peter Creasey [EMAIL PROTECTED] wrote:
The following code calling numpy v1.0.4 fails to terminate on my machine,
which was not
On Nov 13, 2007 2:37 AM, David Cournapeau [EMAIL PROTECTED] wrote:
Geoffrey Zhu wrote:
Yes, with the MSI I can always reproduce the problem with
numpy.test(). It always hangs.With the egg it does not hang. Pointer
problems are usually random, but not random if we are using the same
Keith Goodman wrote:
On Nov 12, 2007 10:51 AM, David Cournapeau [EMAIL PROTECTED] wrote:
On Nov 13, 2007 3:37 AM, Keith Goodman [EMAIL PROTECTED] wrote:
On Nov 12, 2007 10:10 AM, Peter Creasey [EMAIL PROTECTED] wrote:
The following code calling numpy v1.0.4 fails to terminate
Hi all,
The following code calling numpy v1.0.4 fails to terminate on my machine,
which was not the case with v1.0.3.1
from numpy import arange, float64
from numpy.linalg import eig
a = arange(13*13, dtype = float64)
a.shape = (13,13)
a = a%17
eig(a)
Regards,
Peter
On Nov 12, 2007 10:10 AM, Peter Creasey [EMAIL PROTECTED] wrote:
The following code calling numpy v1.0.4 fails to terminate on my machine,
which was not the case with v1.0.3.1
from numpy import arange, float64
from numpy.linalg import eig
a = arange(13*13, dtype = float64)
Works fine on my computer (Mac OS X 10.4), Python
2.4. Runs in a second or so.
-- Lou Pecora
---Peter wrote:
Hi all,
The following code calling numpy v1.0.4 fails to
terminate on my machine, which was not the case with
v1.0.3.1
from numpy import arange, float64
from numpy.linalg
On Nov 13, 2007 3:37 AM, Keith Goodman [EMAIL PROTECTED] wrote:
On Nov 12, 2007 10:10 AM, Peter Creasey [EMAIL PROTECTED] wrote:
The following code calling numpy v1.0.4 fails to terminate on my machine,
which was not the case with v1.0.3.1
from numpy import arange, float64
from
On Nov 12, 2007 12:37 PM, Keith Goodman [EMAIL PROTECTED] wrote:
On Nov 12, 2007 10:10 AM, Peter Creasey [EMAIL PROTECTED] wrote:
The following code calling numpy v1.0.4 fails to terminate on my machine,
which was not the case with v1.0.3.1
from numpy import arange, float64
Geoffrey Zhu wrote:
On Nov 12, 2007 12:37 PM, Keith Goodman [EMAIL PROTECTED] wrote:
On Nov 12, 2007 10:10 AM, Peter Creasey [EMAIL PROTECTED] wrote:
The following code calling numpy v1.0.4 fails to terminate on my machine,
which was not the case with v1.0.3.1
from numpy import arange,
On Nov 12, 2007 10:26 PM, David Cournapeau [EMAIL PROTECTED] wrote:
Geoffrey Zhu wrote:
On Nov 12, 2007 12:37 PM, Keith Goodman [EMAIL PROTECTED] wrote:
On Nov 12, 2007 10:10 AM, Peter Creasey [EMAIL PROTECTED] wrote:
The following code calling numpy v1.0.4 fails to terminate on my machine,
21 matches
Mail list logo
