> Glad you solved it. Can you tell us the details of your setup (gcc
> version, Cygwin version)?
I used the latest mingw 20110316. I can't find out how to get the gcc and cygwin version number though... what are the commands in windows?
Cheers
Wieland
___
I succeeded now in installing the latest Numpy version. There was some
problem in mingw32ccompiler.py. I had to change the lines
elif self.gcc_version < "4.":
self.set_executables(compiler='gcc -mno-cygwin -O2 -Wall',
compiler
I have deinstalled scipy, numpy and Python(x,y), reinstalled a newer
version of Python (x,y) and run the python install again - same result.
However, maybe the build cache was still not cleaned?
I used the build command
>
python setup.py config --compiler=mingw32 build --compiler=mingw32 inst
Dear Ralf,
thanks for you suggestion - the SVN was of course only the numpy master
branch. I switched to the latest 1.6.x branch but the compilation stops with
> ValueError: invalid version number '4.'
in line 107, C:\Python26\lib\distutils\version.py
(before was line 40, self.parse(vstring)).
Hello,
I am glad Mark was able to resolve the bug in einsum very fast since I
am heavily relying on this function. I am working on a Windows 7 64 bit
system with latest Python 2.6. I tried to build numpy from SVN following
along
http://www.scipy.org/Build_for_Windows
After installing numpy I r
Thanks for your reply! I managed to open a ticket,
http://projects.scipy.org/numpy/ticket/1834
You are actually right, you can also just use zeros instead of random.
Maybe I can test a bit more tomorrow... but its 4am in the morning now ;-).
Thanks for your help and kindness!
Wieland
It also fails for
T = random.random((2,d,d))
W = random.random((2,d,d,i))
and d > 2. For d = 3 it fails for i = 911...1365.
Should I submit this as a bug (if so, how do I do that?) and/or
contact the author Mark Wiebe?
Wieland
PS: How
> The equality being that the _expression_ should be ~0?
Exactly.
> I see the problem when the last index is in the range 235 - 390.
Good to see I am not the only one - I was getting crazy. Same range for me by the way.
> Out of curiosity, which machine/OS are you using? I'm
> The equality being that the _expression_ should be ~0?
Exactly.
> I see the problem when the last index is in the range 235 - 390.
Good to see I am not the only one - I was getting crazy. Same range for me by the way.
> Out of curiosity, which machine/OS are you using? I'm on 64 b
Hello,
I am encountering a very strange behaviour of einsum on my machine. I
tracked the problem down to the following test code:
from numpy import *
T = random.random((3,10,10))
W = random.random((3,10,7,275))
print all(einsum('ij...,j...->i...',T[0],W[0]) +
einsum('ij...,j...->i...',T[1],W[1
10 matches
Mail list logo
