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
On Sat, Jan 3, 2009 at 10:13 AM, Mike Landis mlandis...@comcast.net 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 =
All,
You'll probably remember that last December, I started rewriting
np.loadtxt and ame up with a series of functions that support missing
data. I tried to copy/paste the code in numpy.lib.io.py but ran into
dependency problems and left it at that. I think that part of the
reason is that
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
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 version. It
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
On Sat, Jan 3, 2009 at 22:20, Mike Landis mlandis...@comcast.net 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,
On Sat, Jan 3, 2009 at 22:38, Mike Landis mlandis...@comcast.net 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__
On Sat, Jan 3, 2009 at 11:42 PM, Robert Kern robert.k...@gmail.com wrote:
On Sat, Jan 3, 2009 at 22:38, Mike Landis mlandis...@comcast.net wrote:
Maybe the following will also be useful... Recall that I completely
deleted numpy and scipy and reinstalled each from their respective
superpacks,
On Sun, Jan 4, 2009 at 1:38 PM, Mike Landis mlandis...@comcast.net 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__
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 -
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 gotchas
12 matches
Mail list logo
