On Monday 02 June 2008 11:45:31 Alan McIntyre wrote:
> We're in the process of switching to nose
> (http://www.somethingaboutorange.com/mrl/projects/nose/) as the test
> framework for 1.2; I'll try to keep an eye on stuff like that and make
> it work properly if I can.
Alan,
Thanks a lot again for
On Mon, 2008-06-02 at 11:03 -0400, Lewis E. Randerson wrote:
> Found the problem.
>
> The pattern in lahey.py differs from the version of Lahey Fujitsu
> compiler I have. Once corrected, the compiler is now found.
Ok, thanks for going through this. Can I ask you one more thing ? Can
you give us
Pierre GM wrote:
> Mmh, there's something wrong in your installation: there shouldn't be any
> ma.py file in numpy.core, nor test_ma.py in in numpy/core/tests.
OK, I'll do a clean-up and try again. this is probably due to having
previously installed a release candidate a while back...
Bingo!:
On Monday 02 June 2008 13:46:42 Christopher Barker wrote:
> HI all,
>
> I missed a bit of the release process, but I thought all the test
> failures had been squashed. However, I just installed the OS-X 1.1.0
> binary, and got:
> >>> import numpy
> >>> numpy.__version__
Mmh, there's something wr
HI all,
I missed a bit of the release process, but I thought all the test
failures had been squashed. However, I just installed the OS-X 1.1.0
binary, and got:
>>> import numpy
>>> numpy.__version__
'1.1.0'
>>>
>>> from numpy import test
>>> test(all=True)
Numpy is installed in
/Library/F
Hi Alan,
Thanks for looking into it.
David
2008/6/2 Alan McIntyre <[EMAIL PROTECTED]>:
> David,
>
> We're in the process of switching to nose
> (http://www.somethingaboutorange.com/mrl/projects/nose/) as the test
> framework for 1.2; I'll try to keep an eye on stuff like that and make
> it wor
numpy.test(level=10,all=0) seems to work fine.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
David,
We're in the process of switching to nose
(http://www.somethingaboutorange.com/mrl/projects/nose/) as the test
framework for 1.2; I'll try to keep an eye on stuff like that and make
it work properly if I can.
Alan
On Mon, Jun 2, 2008 at 11:20 AM, David Huard <[EMAIL PROTECTED]> wrote:
> H
On Mon, Jun 2, 2008 at 9:20 AM, David Huard <[EMAIL PROTECTED]> wrote:
> Hi,
>
> There are 2 problems with NumpyTest
>
> 1. It fails if the command is given the file name only (without a directory
> structure)
>
> E.g.:
>
> [EMAIL PROTECTED]:~/repos/numpy/numpy/tests$ python test_ctypeslib.py
> Tr
Hi,
There are 2 problems with NumpyTest
1. It fails if the command is given the file name only (without a directory
structure)
E.g.:
[EMAIL PROTECTED]:~/repos/numpy/numpy/tests$ python test_ctypeslib.py
Traceback (most recent call last):
File "test_ctypeslib.py", line 87, in
NumpyTest().
Found the problem.
The pattern in lahey.py differs from the version of Lahey Fujitsu
compiler I have. Once corrected, the compiler is now found.
P.S. One of the libraries defined in the file is also incorrect.
Once I have gotten all the way through the SciPy build and
the users have said all w
Here's fuller output from the lahey.py script.
python
/usr/pppl/python/2.5.2/lib/python2.5/site-packages/numpy/distutils/fcompiler/
lahey.py
customize LaheyFCompiler
find_executable('lf95')
Found executable /usr/pppl/lff95/6.20c/bin/lf95
exec_command(['/usr/pppl/lff95/6.20c/bin/lf95', '--version']
Hi,
When executing numpy/distutils/fcompiler/lahey.py,
I get "none"
Here is what I get from the following command. Note the
Lahey entry under:
Compilers available for this platform, but not found:
available compilers ==
python setup.py config_fc --help-f
On Monday 02 June 2008 08:03:15 Hanno Klemm wrote:
> thanks for your replies, the view works fine. The reason why I like
> recarrays is that you can address your fields simply with a.Name, when
> a is your array. I find that highly convenient when working with data
> interactively.
>
> As far as I
Lewis E. Randerson wrote:
> I am seeing these warnings:
> warning: build_ext: f77_compiler=lahey is not available.
>
>
Hi Lewis,
What happens when you execute directly the file
numpy/distutils/fcompiler/lahey.py ?
cheers,
David
__
Excellenm, thanks for clearing all that up.
How about numpy with 2.6, any issues?
Hanni
2008/6/2 David Cournapeau <[EMAIL PROTECTED]>:
> Hanni Ali wrote:
> >
> > Yes I had used the internal versions in the mean time, but I do want
> > to try to use the intel fortran compiler in all likelyhood.
Hi,
When trying to build numpy 1.1.0 with python 2.5.2 on an RHEL3 32-bit
system, using command:
python setup.py config_fc --fcompiler=lahey install &> install_LEW.log
I am seeing these warnings:
warning: build_ext: f77_compiler=lahey is not available.
and
warning: build_ext: extension
Francesc, Pierre,
thanks for your replies, the view works fine. The reason why I like
recarrays is that you can address your fields simply with a.Name, when
a is your array. I find that highly convenient when working with data
interactively.
As far as I know there is no similar possbility to do
Hanni Ali wrote:
>
> Yes I had used the internal versions in the mean time, but I do want
> to try to use the intel fortran compiler in all likelyhood.
Yes, people can try to build as they want, that's the beauty of open
source :) But for official distribution, I don't want to depend on non
f
Hi David,
> I can't build official binaries with VS: I don't have VS. Also, there is
> the problem of building the fortran dependencies (BLAS/LAPACK). I don't
> know if it is even possible to build ATLAS on windows x64. Even assuming
> we only use netlib BLAS/LAPACK, I still need a fortran comp
Hanni Ali wrote:
>
> I had managed to compile and install 1.04 with vs 2005 64 bit with a
> bit of hacking,
I can't build official binaries with VS: I don't have VS. Also, there is
the problem of building the fortran dependencies (BLAS/LAPACK). I don't
know if it is even possible to build ATL
Hi David,
> Unfortunately, this is difficult: windows 64 is not commonly available
> (I don't have any access to it personally, for example), and mingw is
> not available yet for windows 64 either.
I had managed to compile and install 1.04 with vs 2005 64 bit with a bit of
hacking, however it h
Bala subramanian wrote:
>
> I dnt understand why python 2.4 dosent contain seperate libraries
> installed in /usr/lib?
>
Because your python 2.4 was installed in /usr/local, I guess:
> The following is the result of the command - python -c "import sys;
> print sys.path"
>
> ['', '/usr/local/lib
Hi,
Where is numpy installation located ? (you should find it with locate numpy)
Matthieu
2008/6/2 Bala subramanian <[EMAIL PROTECTED]>:
> Dear David,
>
> I gave the following and pressed TAB, it seems that i have two python
> installation in my linux.
>
> $ python
>
> python python2 python2.2
Dear David,
I gave the following and pressed TAB, it seems that i have two python
installation in my linux.
$ python
python python2 python2.2 python2.4 pythonsh
When i give python, python 2.4.3 interpreter opens
When i give python2, python 2.2.3 interpreter opens
The default is python 2.4.3.
25 matches
Mail list logo
