Hi,
Excellent job!
I got NO errors (including Vista), all tests passed .
I did see different 'sse' packages installed for the different
processors (given below) that mainly cover AMD Athlon processors and
different favors of SSE. Everything was done using Python 2.5.2
installer from the official
David Cournapeau wrote:
> Jarrod Millman wrote:
>> Hello,
>>
>> David Cournapeau has prepared a new win32 installer, which is aimed at
>> solving the recurring problem of non working atlas on different sets
>> of CPU. This installer simply checks which cpu you have, and installs
>> the appropriate
Yes, I am one of those users with crashes in numpy 1.4. Your build
seems to pass for me. For reference my machine is Windows XP, Intel
Xeon 5140
-
Numpy is installed in C:\Python25\lib\site-packages\numpy
Numpy version 1.0.5.dev5008
Python version 2.5.2 (r252:60911, Feb 21 2008, 13
Neil Crighton wrote:
> The Win32 installer works on my Vista machine. There is one failed
> test, but I think that's just because it tries to write somewhere it
> doesn't have permission - I installed Python in /Program
> Files/Python25/, and you need to be an administrator to write to
> Program F
Bruce Southey wrote:
> Hi,
> The installer requires 2.5 but that is not explicitly stated. Given
> that numpy and scipy technically require Python 2.3 as a minimum, the
> installer should support Python 2.3 and Python 2.4. Otherwise, it
> needs to clearly state that Python 2.5 is a must.
>
Stri
Hi,
The installer requires 2.5 but that is not explicitly stated. Given
that numpy and scipy technically require Python 2.3 as a minimum, the
installer should support Python 2.3 and Python 2.4. Otherwise, it
needs to clearly state that Python 2.5 is a must.
I did install Python 2.5.2 on my WIndows
The Win32 installer works on my Vista machine. There is one failed
test, but I think that's just because it tries to write somewhere it
doesn't have permission - I installed Python in /Program
Files/Python25/, and you need to be an administrator to write to
Program Files/.
Here's the error messag
On Sun, Apr 13, 2008 at 8:24 PM, David Cournapeau
<[EMAIL PROTECTED]> wrote:
> I think I got the problem. Now, I got it working on my two vmware
> windows at hand. Could you try this:
>
>
> http://www.ar.media.kyoto-u.ac.jp/members/david/archives/numpy-superpack-python2.5.exe
Did you have a pr
Everything installed without problem on Intel Pentium M on my notebook
recognized as SSE2 capable.
Installer found Python 2.5. immediately, which I just installed and
all my windows environment settings are still setup for python 2.4
Thanks,
Josef
>>> numpy.test()
Numpy is installed in C:\Progra
Tested fine on my old Classic Athlon 500 (no SSE) under Win98. It
correctly reported installing the non-SSE version when I clicked on the
details button on the last page of the install wizard. Whereas
previously numpy.test() would bring up an illegal operation dialog box,
now all tests pass. Ni
On Mon, Apr 14, 2008 at 1:08 PM, David Cournapeau
<[EMAIL PROTECTED]> wrote:
> Bill Baxter wrote:
> > Seems to work here now, too!
> >
> > It doesn't tell you in an easy to see place what version of SSE it
> > decides to use. Do you think that's ok?
>
> I simply did not think it was useful in
Bill Baxter wrote:
> Seems to work here now, too!
>
> It doesn't tell you in an easy to see place what version of SSE it
> decides to use. Do you think that's ok?
I simply did not think it was useful information. How would you like to
get the information ? To be honest, I do not want to spend t
Seems to work here now, too!
It doesn't tell you in an easy to see place what version of SSE it
decides to use. Do you think that's ok? (You can tell by looking at
the "details" at then end of installation, though.
Is there some way to tell this info from inside NumPy itself? If so
then maybe
Bill Baxter wrote:
>
> That's right. No execution and no error. The installer finishes
> (quite quickly!)
Doing nothing is quick, even on windows :)
> as if it did everything according to plan.
>
> Anything I can do to help you track down the problem? It's a Win XP system.
I think I got the
Bill Baxter wrote:
> What's the installer supposed to do?
> It appears to have decided I have SSE3 extracted an sse3 exe to
> somewhere, and then quit without doing anything else. I can't seem to
> find where it put the numpy-1.0.5-sse3.exe it extracted, either.
>
> The details, say "Execute: nump
On Mon, Apr 14, 2008 at 10:57 AM, David Cournapeau
<[EMAIL PROTECTED]> wrote:
> Bill Baxter wrote:
> > What's the installer supposed to do?
>
> It is supposed to install numpy :) The fact that it is not clear is not
> good, obviously. Suggestions to make it more obvious are welcomed.
>
>
> > It
Bill Baxter wrote:
> What's the installer supposed to do?
It is supposed to install numpy :) The fact that it is not clear is not
good, obviously. Suggestions to make it more obvious are welcomed.
> It appears to have decided I have SSE3 extracted an sse3 exe to
> somewhere, and then quit withou
Damian Eads wrote:
> Hi David,
>
> I'd be happy to help you test the installer (and let you know what my
> processor supports). Is it just the installer you want tested or do you
> also want us to try some computation with numpy?
>
Doing numpy.test() should be fine. The actual numpy installer
David Cournapeau wrote:
> Jarrod Millman wrote:
>> Hello,
>>
>> David Cournapeau has prepared a new win32 installer, which is aimed at
>> solving the recurring problem of non working atlas on different sets
>> of CPU. This installer simply checks which cpu you have, and installs
>> the appropriate
What's the installer supposed to do?
It appears to have decided I have SSE3 extracted an sse3 exe to
somewhere, and then quit without doing anything else. I can't seem to
find where it put the numpy-1.0.5-sse3.exe it extracted, either.
The details, say "Execute: numpy-1.0.5-sse3.exe" but no execu
On Mon, Apr 14, 2008 at 10:07 AM, David Cournapeau
<[EMAIL PROTECTED]> wrote:
> Jarrod Millman wrote:
> > Hello,
> >
> > David Cournapeau has prepared a new win32 installer, which is aimed at
> > solving the recurring problem of non working atlas on different sets
> > of CPU. This installer si
Jarrod Millman wrote:
> Hello,
>
> David Cournapeau has prepared a new win32 installer, which is aimed at
> solving the recurring problem of non working atlas on different sets
> of CPU. This installer simply checks which cpu you have, and installs
> the appropriate numpy accordingly (without atlas
Hello,
David Cournapeau has prepared a new win32 installer, which is aimed at
solving the recurring problem of non working atlas on different sets
of CPU. This installer simply checks which cpu you have, and installs
the appropriate numpy accordingly (without atlas if your cpu is not
supported). W
23 matches
Mail list logo
