You have to look int them and change the imports. For example ==== modules/package/a.py import package.b ==== end ==== modules/package/b.py import package.a ==== end
must be changed into ==== modules/package/a.py import b ==== end ==== modules/package/b.py import a ==== end because package is not in path (unless you follow Jonathan advice and you put it in site-packages). for the record, this is because sys.path is not thread safe and we cannot app all apps to sys.path without generating conflicts. On Mar 30, 5:21 pm, "[email protected]" <[email protected]> wrote: > So what can I do to fix this. These modules would have to be in the folder > modulesbecause I'm going to play such an application on Google App Engine. > _____________________________________________ > *Gilson Filho* > *Web Developerhttp://gilsondev.com* > > 2011/3/30 Massimo Di Pierro <[email protected]> > > > > > > > > > I believe the problem is that the module expects to be in sys.path. > > Some python modules are very selfish and assume that. > > > On Mar 30, 12:12 pm, "[email protected]" > > <[email protected]> wrote: > > > I researched the list of the error of using local_import (), but without > > > success. I used the "import applications.app.modules.script as Script" > > and > > > other ideas did not work. Howshould I do about it? > > > > The error: ImportError: No module named testapp.modules.FormatTweets > > > > _____________________________________________ > > > *Gilson Filho* > > > *Web Developerhttp://gilsondev.com*
