Re: [Numpy-discussion] building numpy/scipy
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__ 'D:\\Programs\\Python25\\lib\\site-packages\\numpy\\__init__.pyc'
import scipy; scipy.__file__ 'D:\\Programs\\Python25\\lib\\site-packages\\scipy\\__init__.pyc'
$ cd site-packages\numpy; python setup.py config This is the wrong setup.py file to run $ cd site-packages\scipy; python setup.py config non-existing path in 'cluster': 'src\\vq_module.c' non-existing path in 'cluster': 'src\\vq.c' non-existing path in 'cluster': 'src\\hierarchy_wrap.c' non-existing path in 'cluster': 'src\\hierarchy.c' Appending scipy.cluster configuration to scipy Ignoring attempt to set 'name' (from 'scipy' to 'scipy.cluster') Warning: No configuration returned, assuming unavailable. Appending scipy.constants configuration to scipy Ignoring attempt to set 'name' (from 'scipy' to 'scipy.constants') could not resolve pattern in 'fftpack': 'src/dfftpack\\*.f' non-existing path in 'fftpack': 'fftpack.pyf' non-existing path in 'fftpack': 'src/zfft.c' non-existing path in 'fftpack': 'src/drfft.c' non-existing path in 'fftpack': 'src/zrfft.c' non-existing path in 'fftpack': 'src/zfftnd.c' non-existing path in 'fftpack': 'src/zfft_fftpack.c' non-existing path in 'fftpack': 'src/drfft_fftpack.c' non-existing path in 'fftpack': 'src/zfftnd_fftpack.c' non-existing path in 'fftpack': 'convolve.pyf' non-existing path in 'fftpack': 'src/convolve.c' Appending scipy.fftpack configuration to scipy Ignoring attempt to set 'name' (from 'scipy' to 'scipy.fftpack') d:\Programs\Python25\lib\site-packages\numpy\distutils\system_info.py:1340: UserWarning: Atlas (http://math-atlas.sourceforge.net/) libraries not found. Directories to search for the libraries can be specified in the numpy/distutils/site.cfg file (section [atlas]) or by setting the ATLAS environment variable. warnings.warn(AtlasNotFoundError.__doc__) d:\Programs\Python25\lib\site-packages\numpy\distutils\system_info.py:1349: UserWarning: Blas (http://www.netlib.org/blas/) libraries not found. Directories to search for the libraries can be specified in the numpy/distutils/site.cfg file (section [blas]) or by setting the BLAS environment variable. warnings.warn(BlasNotFoundError.__doc__) d:\Programs\Python25\lib\site-packages\numpy\distutils\system_info.py:1352: UserWarning: Blas (http://www.netlib.org/blas/) sources not found. Directories to search for the sources can be specified in the numpy/distutils/site.cfg file (section [blas_src]) or by setting the BLAS_SRC environment variable. warnings.warn(BlasSrcNotFoundError.__doc__) Traceback (most recent call last): File "setup.py", line 32, in <module> setup(**configuration(top_path='').todict()) File "setup.py", line 8, in configuration config.add_subpackage('integrate') File "d:\Programs\Python25\lib\site-packages\numpy\distutils\misc_util.py", line 851, in add_subpackage caller_level = 2) File "d:\Programs\Python25\lib\site-packages\numpy\distutils\misc_util.py", line 834, in get_subpackage caller_level = caller_level + 1) File "d:\Programs\Python25\lib\site-packages\numpy\distutils\misc_util.py", line 781, in _get_configuration_from_setup_py config = setup_module.configuration(*args) File "D:\Programs\Python25\Lib\site-packages\scipy\integrate\setup.py", line 10, in configuration blas_opt = get_info('blas_opt',notfound_action=2) File "d:\Programs\Python25\lib\site-packages\numpy\distutils\system_info.py", line 267, in get_info return cl().get_info(notfound_action) File "d:\Programs\Python25\lib\site-packages\numpy\distutils\system_info.py", line 416, in get_info raise self.notfounderror,self.notfounderror.__doc__ numpy.distutils.system_info.BlasNotFoundError: Blas (http://www.netlib.org/blas/) libraries not found. Directories to search for the libraries can be specified in the numpy/distutils/site.cfg file (section [blas]) or by setting the BLAS environment variable. At 10:40 PM 1/3/2009, you wrote:
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 would be helpful to see your actual error messages from nose, with copy and paste, at least the first few and last parts of the nose tests. Your summary error message is not very helpful because it doesn't show your actual error path and trace backs.
When I installed the 0.7.0 b1 superpack on WindowsXP, it worked out of the box. The only thing to do, before installing a new version of numpy or scipy, is to uninstall or delete any old version in site-packages, since the directory names of scipy and numpy do not include version numbers. Installing on top of an old version, can leave some old files around which sometimes cause errors.
Josef _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
On Sat, Jan 3, 2009 at 22:38, Mike Landis <mlandis001@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__ 'D:\\Programs\\Python25\\lib\\site-packages\\numpy\\__init__.pyc'
import scipy; scipy.__file__ 'D:\\Programs\\Python25\\lib\\site-packages\\scipy\\__init__.pyc'
$ cd site-packages\numpy; python setup.py config This is the wrong setup.py file to run
That message is correct. Don't do that. You don't run the setup.py scripts on installed binaries.
$ cd site-packages\scipy; python setup.py config
Don't do that either. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
On Sat, Jan 3, 2009 at 11:42 PM, Robert Kern <robert.kern@gmail.com> wrote:
On Sat, Jan 3, 2009 at 22:38, Mike Landis <mlandis001@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__ 'D:\\Programs\\Python25\\lib\\site-packages\\numpy\\__init__.pyc'
import scipy; scipy.__file__ 'D:\\Programs\\Python25\\lib\\site-packages\\scipy\\__init__.pyc'
$ cd site-packages\numpy; python setup.py config This is the wrong setup.py file to run
That message is correct. Don't do that. You don't run the setup.py scripts on installed binaries.
$ cd site-packages\scipy; python setup.py config
Don't do that either.
-- Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
Mike, don't go in site-packages at all, except for browsing and looking at the source for information. basic steps: run installer go to a working directory, not under the python directory in programs, (and without any scipy, numpy source in it) then start python or idle there and then import numpy and scipy and test, that's it. Unless there is a reason for you to change the numpy, scipy source there is no reason for you to touch any of the config, compile build steps. They are for later, when you need additional packages that don't have an installer. To get up and running, I recommend just to follow the basic steps for a user. Josef
On Sun, Jan 4, 2009 at 1:38 PM, Mike Landis <mlandis001@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__ 'D:\\Programs\\Python25\\lib\\site-packages\\numpy\\__init__.pyc'
import scipy; scipy.__file__ 'D:\\Programs\\Python25\\lib\\site-packages\\scipy\\__init__.pyc'
At this stage, you're *done*. Everything is installed, you don't have to do anything anymore. I am sorry if the following is obvious, but that's the only explanation I can make: there are two ways to install open source softwares - from sources, or from binary installers. By using the superpack, you are using the later - using setup.py implied the former. So what you end up doing is to try building the software from the binary - which does not make sense. It may not look like it at this point, but you are making things much more complicate than they really are :) After the super pack executions, you have run the installers successfully, so everything is installed, without any further step to follow. cheers, David
participants (4)
-
David Cournapeau -
josef.pktd＠gmail.com -
Mike Landis -
Robert Kern