Import failed when the module is already in the sys.path

Question

Hi all:

It's weird to me that the import fails even when it's in the sys.path.

today, I set up a google app engine django environment on ubuntu in my lab's pc. And it works fine when I checked out the code and ran it in windows(same pc in the lab).

But when I went to the dorm, and checked out the code and start to run, it failed weirdly.

I print the sys.path, like this:

['/home/tower/googlecode/mygae', '/home/tower/googlecode/mygae/.google_appengine', '/home/tower/googlecode/mygae/.google_appengine/lib/antlr3', ...]

and when I ran python complained

from google.appengine.api import apiproxy_stub_map
ImportError: No module named appengine.api

it's easy to know the google module is in the '/home/tower/googlecode/mygae/.google_appengine' directory, and the __init__.py for each module is present.

So what can be the reason for this weird thing? Or what I messed up probably?

thanks.

Answer 1

Sometimes you can get an import error for a module when the error is something different, like a syntax error. Try putting

import pdb;pdb.set_trace()

just before the import and then s(tep) into the import, and n(ext) thruogh the module in question to see of you get an error.

Answer 2

Can you import google and google.appengine? Are you sure interpreter has read and traverse access rights to the module tree?

Answer 3

Looks like you're getting a module (or package) called 'google' from elsewhere -- perhaps /home/tower/googlecode/mygae -- and THAT google module has no appengine in it. To check, print google.__file__ and if possible google.__path__; that should be informative.