Re: [Swig-user] Python unable to find module

[Josh C. <jc...@nc...>]

On Mon, 8 Jan 2007, Julian wrote:

> I didn't get any response to my earlier post so I'm thinking maybe I should
> pose my problem differently:
> What makes a module invalid? I have a dll named '_example.pyd' that was
> created using swig 1.3.31 and I'm using python 2.5 But I still get this
> error : no module named example So, is there any way to find out exactly why
> it cannot find the module ?
> Is there some way where the python interpreter gives out more debugging
> information?

The module that Python couldn't find was "example", not "_example", so 
it's example.py that's relevant.  Modules have to be located in a place 
where Python knows to look for them.  You probably need to move your 
modules to someplace on Python's search path or change that search path 
(e.g., by changing your PYTHONPATH environment variable).  This doesn't 
really have anything to do with SWIG.

Josh