On Fri, Sep 11, 2009 at 2:22 PM, Sebastian <seb...@gmail.com> wrote: > Hello, > > The folks at stsci (Jim T.) are not able to reproduce this error with > 1.4.0.dev7362 so I guess there is something wrong with my numpy > installation. > I also tried '1.4.0.dev7362' and numpy1.3 (stable) but alas, the same > error! > > My system: > [r...@siate numpy]# uname -a > Linux siate.iate.oac.uncor.edu 2.6.27.25-78.2.56.fc9.x86_64 #1 SMP Thu Jun > 18 12:24:37 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux > > Below is the numpy error and the the output of numpy, build and install as > attached: > python setup.py build > build.txt > python setup.py install > install.txt > > Can't work out what is going wrong here. I don't think I'm missing some > dependency nor mixing compilers, but maybe I'm wrong, any hints? > best regards, > - Sebastian Gurovich > > > [r...@siate soft]# ipython > Python 2.5.1 (r251:54863, Jun 15 2008, 18:24:56) > Type "copyright", "credits" or "license" for more information. > > IPython 0.8.3 -- An enhanced Interactive Python. > ? -> Introduction and overview of IPython's features. > %quickref -> Quick reference. > help -> Python's own help system. > object? -> Details about 'object'. ?object also works, ?? prints more. > > In [6]: numpy.__version__ > Out[6]: '1.4.0.dev7375' > > In [7]: a=numpy.zeros(0x80000000,dtype='b1') > > I expect 0x80000000 is interpreted by python as a negative number. Try 2**31 intead.
Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
