[SciPy-user] ImportError: No module named __config__

[Mark Coletti]

On Mon, Mar 24, 2008 at 7:45 AM, Matthew Brett <matthew.brett at gmail.com>
wrote:

> Hi,
>
> Did you see this message just sent by David Cournapeau in response to
> similar question?


I saw, but dismissed the question since I thought this was a scipy, not a
numpy problem.


>
> On Mon, Mar 24, 2008 at 12:22 PM, Mark Coletti <mcoletti at gmail.com> wrote:
> > I've just installed scipy 0.6.0 but am unable to use it.  When
> attempting to
> > import scipy, I get the following error:
>

[...]


>
> >   File "scipy/__init__.py", line 54, in <module>
> >     from __config__ import show as show_config
> > ImportError: No module named __config__
>
> Mark Coletti wrote:
> >
> > I'm having the same problem with my SuSE 10.1 box. [...]
>
> This is because you are trying to import numpy while being in the numpy
> source tree, which does not work. The solution is to simply relaunch
> your python interpreter from another directory. The last svn has a
> better error message, because the above error is indeed quite obscure.
>

And I also dismissed his message because I wasn't in the numpy source tree.
;)

However, I changed the /usr/bin/python symbolic link to refer to the newer
2.5.4 python in /usr/local/bin (since SuSE won't bother to update the
10.1native python to
2.5, so upgrading via YaST is futile).  That *seemed* to help.  So it may
very well have been some issue with two versions of python conflicting with
one another.  (I had set the execution paths to prefer the newer python, but
forgot that some scripts have the old python hard-coded in their bang line.
Urgh.)

Of course I've run into another problem, which I'll relate in a separate
e-mail.  Oh, the joys of legacy code.  :)

Cheers!

Mark
-- 
I'm taking reality in small doses to build immunity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20080324/69026c61/attachment.html>