Sorry its not really a bug. I understood why . It's an integer and I'm doing
an overflow. Perhaps an error message can be printed or an automatic change
(with a warning) can be done. I think that I prefer to loose the type but
keep the value correct.
N.
___
Hello,
when doing some test I saw a very important bug in numpy (at least on the svn
version and 1.0.3 (ubuntu package)).
I'm using a svn version of numpy:
In [31]: numpy.__version__
Out[31]: '1.0.5.dev4767'
The problem is for an array larger than 256*256 the su
It's working fine thank you. I'm a little bit surprised because I was thinking
that the --fcompiler when building numpy was the way to change the default
compiler but anyway, that's work now.
N.
>
> Tell f2py that you want it to use gfortran instead of the default.
>
> f2py --fcompiler=gnu95 -
This is the log I have when I'm trying to use f2py with a fortran 90 file.
The last line seems to tell me that f2py cannot see gfortran and g95 even if
it detected them when I installed f2py.
thanks,
N.
gfortran and g95 are installed and I can use them:
> gfortran
gfortran: no input files
>g
I have already gfortran and g95 installed and working fine for all the system
but numpy and scipy.
By the way I'm using linux not MacOSX. My problem is that when I'm installing
numpy gfortran (or g95) is detected but not at all the step and so f2py seem
to be unable to use it.
look at:
line
Hello,
I'm using the last svn version of numpy (.
I tried the solution found on the mail list:
python setup.py config_fc --fcompiler=gnu95 build
the two interesting part (at least for me) in the building process are:
customize GnuFCompiler Found executable /usr/bin/g77
gnu: no
Thank you to both of you for this explanatin. I'm coming from the fortran
world and so I never had to deal with this before...
Sorry to have polluate the list for a stupid things
Thanks again that clarify the problem
Nicolas
Le Thursday 08 February 2007 17:01:36 Travis Oliphant, vous avez é
I have a big problem with numpy, numarray and Numeric (all version)
If I'm using the script at the bottom, I obtain these results:
var1 before function is [3 4 5]
var2 before function is 1
var1 after function must be [3 4 5] is [ 9 12 15] <-- problem
var2 after function must be 1 is 1
Hi,
I think that the following command and result are a little bit inconsistant
and a source of error. I don't understand why: dtype=float32 for a result
when it's invalid in the definition.
N.
In [8]: a = numpy.array([1],dtype=float32)
--
