Mike Landis wrote:
> I cd'd out of numpy and site-packages and re-ran the package
> tests. both numpy.test() and scipy.test() ran without serious
> errors. Some DeprecationWarnings and integrals that are probably
> divergent or slowly convergent...
>
> It's looking much more promising. Two go
I cd'd out of numpy and site-packages and re-ran the package
tests. both numpy.test() and scipy.test() ran without serious
errors. Some DeprecationWarnings and integrals that are probably
divergent or slowly convergent...
It's looking much more promising. Two gotchas on top of each other -
On Sun, Jan 4, 2009 at 1:38 PM, Mike Landis wrote:
> Maybe the following will also be useful... Recall that I completely
> deleted numpy and scipy and reinstalled each from their respective
> superpacks, then ran:
>
> >>> import numpy; numpy.__file__
> 'D:\\Programs\\Python25\\lib\\site-packages
On Sat, Jan 3, 2009 at 11:42 PM, Robert Kern wrote:
> On Sat, Jan 3, 2009 at 22:38, Mike Landis wrote:
>> Maybe the following will also be useful... Recall that I completely
>> deleted numpy and scipy and reinstalled each from their respective
>> superpacks, then ran:
>>
>> >>> import numpy; nu
On Sat, Jan 3, 2009 at 22:38, Mike Landis wrote:
> Maybe the following will also be useful... Recall that I completely
> deleted numpy and scipy and reinstalled each from their respective
> superpacks, then ran:
>
> >>> import numpy; numpy.__file__
> 'D:\\Programs\\Python25\\lib\\site-packages\\
Maybe the following will also be useful... Recall that I completely
deleted numpy and scipy and reinstalled each from their respective
superpacks, then ran:
>>> import numpy; numpy.__file__
'D:\\Programs\\Python25\\lib\\site-packages\\numpy\\__init__.pyc'
>>> import scipy; scipy.__file__
'D:
On Sat, Jan 3, 2009 at 22:20, Mike Landis wrote:
> Josef (sorry about spelling your name wrong in a previous post),
>
> Thanks for the continued suggestions. I deleted the site-packages:
> numpy and scipy, and reinstalled each using the current release
> superpacks (numpy first, then scipy).
>
>
Josef (sorry about spelling your name wrong in a previous post),
Thanks for the continued suggestions. I deleted the site-packages:
numpy and scipy, and reinstalled each using the current release
superpacks (numpy first, then scipy).
then I ran:
python -c 'import numpy; numpy.test()'
and got
Make sure that when you import scipy that you get the correct version.
>>> import scipy
>>> scipy.__file__
'C:\\Programs\\Python25\\lib\\site-packages\\scipy\\__init__.pyc'
>From your error messages, I would think python is loading the source
distribution and not the compiled and installed versio
Thanks for the suggestion Joseph - the scipy test suite runs, but it
produces lots of errors.
Some deprecation warnings in numpy\lib\utils.py (line 110) and
scipy\linalg\decomp.py (line 1173)
Than it complains about a '_bad_path_' (doesn't exist or not
writable). Couldn't remove
\appdata]loc
On Sat, Jan 3, 2009 at 10:13 AM, Mike Landis wrote:
> I do not have cygwin in my windows path, so I guess that's already hidden.
>
> I patched d:\programs\python25\lib\distutils\cygwinccompiler.py, line 424
> to read
>
> ld_version = StrictVersion(result.group(1).rsplit('.',1)[0])
>
> but I still
I do not have cygwin in my windows path, so I guess that's already
hidden.
I patched d:\programs\python25\lib\distutils\cygwinccompiler.py,
line 424 to read
ld_version = StrictVersion(result.group(1).rsplit('.',1)[0])
but I still got crash and a traceback.
David Cournapeau suggested using the s
Mike Landis wrote:
> Cygwin is present, so not just the dumbed down Windows CMD available.
You should not use cygwin: if you use cygwin, it will build numpy
against the cygwin python, or worse, will be very confused, because you
will mix cygwin compilers and mingw compilers. Unless you want to bu
On Sat, Jan 3, 2009 at 1:07 AM, Mike Landis wrote:
> Cygwin is present, so not just the dumbed down Windows CMD available.
>
> I ran the numpy-1.2.1 superpak. Verified that it installed (cause you don't
> get near as much output as you do from a shell prompt) by running:
>
>"
>
> python -c 'i
Cygwin is present, so not just the dumbed down Windows CMD
available.
I ran the numpy-1.2.1 superpak. Verified that it installed (cause
you don't get near as much output as you do from a shell prompt) by
running:
"python -c 'import numpy; print numpy.__version__
'"
and got the numpy version n
On Sat, Jan 3, 2009 at 12:10 PM, Mike Landis wrote:
> Maybe the reason I'm having trouble is that I'm trying to get it
> working on Windows, when almost everyone else is running on Linux?
It is true that most developers use some sort of unix (linux, mac os
X), but we definitely try to make sure i
On Sat, Jan 3, 2009 at 2:07 PM, Mike Landis wrote:
> Does it sort of non-destructively overlay the 2.5 that I'm already running?
>
It only installs numpy into your existing python installation - it
will not overwrite anything else in your python installation (e.g.
everything else should work as b
Does it sort of non-destructively overlay the 2.5 that I'm already running?
At 11:45 PM 1/2/2009, you wrote:
>There is a superpack for the python2.5 at the same page. Again a
>binary .exe file that should make the installing a fair bit easier.
>
>Cheers
> Tommy
>
>On Jan 2, 2009, at 11:26 PM,
There is a superpack for the python2.5 at the same page. Again a
binary .exe
file that should make the installing a fair bit easier.
Cheers
Tommy
On Jan 2, 2009, at 11:26 PM, Mike Landis wrote:
> Have to use Pyton 2.5 because I'm also using web2py. Python 2.5 and
> a bunch of packages th
Have to use Pyton 2.5 because I'm also using web2py. Python 2.5 and
a bunch of packages that depend on it are already installed.
At 11:05 PM 1/2/2009, you wrote:
> >
>
>Is there any reason why you can not use the numpy-1.2.1-win32-
>superpack-python2.4.exe
>from the
>http://sourceforge.net/proj
>
Is there any reason why you can not use the numpy-1.2.1-win32-
superpack-python2.4.exe
from the
http://sourceforge.net/project/showfiles.php?group_id=1369&package_id=175103
download page? I think that is what Mr. Kern meant by using the
binaries. This will install
already built code into the
Maybe the reason I'm having trouble is that I'm trying to get it
working on Windows, when almost everyone else is running on Linux? I
have cygwin with f77, g++, make, ... installed, but it's definitely
not a Linux machine. I'm working from the windows install
documentation page. Maybe there
David,
You say "you should really use the distributed binaries" but I
don't know how to accomplish even that from the install directions.
The Installing_SciPy page doesn't say what to do when you get errors or
which warnings you can live with, so I don't know how to troubleshoot the
install.
If
So, on page
<
http://www.scipy.org/Installing_SciPy/Windows#head-c7b42e8bc6116eb8108df13a49ab1ef6a883
>, what are the unspoken instructions that everyone else seems to know
about (except me) that should be implemented between defining
.numpy-site.cfg and running
python setup.py config in the
2009/1/2 Mike Landis :
> Some of the install instructions are kind of ambiguous.
>
> When a library name ends in .a or .dll, it's obvious what it is, but
> 'library' is sometimes used generically without indicating whether
> you're talking about static or dynamic, e.g. how does numpy/scipy
> link t
On Sat, Jan 3, 2009 at 3:29 AM, Mike Landis wrote:
> Some of the install instructions are kind of ambiguous.
>
> When a library name ends in .a or .dll, it's obvious what it is, but
> 'library' is sometimes used generically without indicating whether
> you're talking about static or dynamic, e.g.
Some of the install instructions are kind of ambiguous.
When a library name ends in .a or .dll, it's obvious what it is, but
'library' is sometimes used generically without indicating whether
you're talking about static or dynamic, e.g. how does numpy/scipy
link to MKL? Is it statically or dyn
27 matches
Mail list logo
