[SciPy-user] advice on scipy installation

[Pearu Peterson]

On Sun, 13 Mar 2005, Darren Dale wrote:

> Hello scipy users,
>
> I am having some trouble with installing scipy-0.3.2, specifically linking to
> atlas. I asked a question about this a month or two ago, and didnt receive a
> response. Please, I would really appreciate some help, and I think I located
> a bug.
>
> First, I have read all the documentation about installing scipy: I am using
> site.cfg to reflect my setup. The output of system_info.py is included at the
> end of this email, all the atlas, lapack, and blas info was found and
> reported (with the exception of blas_src_info and lapack_src_info, which are
> not available on my machine). So up to this point, things look good.
>
> The trouble starts when I try to run python setup.py build. At this point I am
> getting NOT AVAILABLE messages, but for packages that system_info.py had just
> successfully queried.
>
> Why would system_info.py report the existence of packages when I run it
> manually, but fail to report the same packages during installation? I think I
> have a lead. site.cfg is not being read during the build, because the
> installer is looking for it at ./site.cfg instead of
> at ./scipy_core/scipy_distutils/site.cfg.
>
> I think the offending line is around line 287 in system_info.py:
>
>        cf = os.path.join(os.path.split(os.path.abspath(__file__))[0],
>                          'site.cfg')
>
> __file__ is ./setup.py during the build,
> and ./scipy_core/scipy_distutils/system_info.py when I call system_info.py.
> Could somebody recommend a fix? Do I copy site.cfg to ./? I dont think this
> is the right thing to do, but I dont know how to point cf to the right
> location (I still have a lot to learn about python).

This bug is now fixed in scipy CVS. The fix is to replace the six lines
starting at line #285 in system_info.py by

         try:
             f = __file__
         except NameError,msg:
             f = sys.argv[0]
         cf = os.path.join(os.path.split(os.path.abspath(f))[0],
                           'site.cfg')

Thanks for reporting this bug!
Pearu