[SciPy-dev] issues with scipy and eggs

Andrew Straw strawman at astraw.com
Sat Dec 10 20:12:59 CST 2005

OK, with your changes, I have
scipy_core- and

But unfortunately not all is well. Here's my latest traceback. Note that
all of scipy works when not installed as an egg, and all my other eggs
work. This is with setuptools 0.6a8.

astraw at hdmg:~$ python
-=-=-=-=-=-=-=-=-=-= python version info -=-=-=-=-=-=-=-=-=-=
2.4.1 /usr

Python 2.4.1 (#2, May  6 2005, 11:22:24)
[GCC 3.3.6 (Debian 1:3.3.6-2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import scipy
UserWarning: Module scipy was already imported from
is being added to sys.path
  tmp_pkg_resources = __import__('pkg_resources')
Importing test to scipy
Importing base to scipy
Importing basic to scipy
>>> import scipy.signal
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
line 11, in ?
    from ltisys import *
line 13, in ?
    import scipy.linalg as linalg
line 10, in ?
    from basic import *
line 18, in ?
    from scipy.lib.lapack import get_lapack_funcs
ImportError: No module named lapack

Robert Kern wrote:

>Andrew Straw wrote:
>>OK, but which "scipy" directory are you talking about?  When I do an svn
>>checkout of full scipy, there is no scipy directory. Only after I do
>>some building is there a "scipy" directory -- below "build".
>Sorry. Lib/__init__.py

More information about the Scipy-dev mailing list