ImportError: No module named django (and django is properly installed on this machine) about jaikuengine HOT 11 CLOSED

There's an incompatibility with the current appengine SDK that is getting 
fixed. Meanwhile, comment out the 
lines

      if FakeFile._skip_files.match(relative_filename):
        logging.warning('Blocking access to skipped file "%s"',
                        logical_filename)
        return False

in google/appengine/tools/dev_appserver.py.

(workaround originally by termie)

Issue 14 has been merged into this issue.

Hi mika, 

Not really in google/appengine/tools/dev_appserver.py, please remember 
jaikuengine
brings its own SDK copy through externals.

For those having this problem just comment out the block cited by Mika in
'.google_appengine/google/appengine/tools/dev_appserver.py' as a workaround. 
Keep in
mind it will produce a diff on an 'external item' (see svn status output).

regards, 
-- stratus

With SDK version 1.1.9, the block 

      if FakeFile._skip_files.match(relative_filename):
        logging.warning('Blocking access to skipped file "%s"',
                        logical_filename)
        return False

is *not* in google/appengine/tools/dev_appserver.py. There doesn't appear to be
anything like it, either. 

thelevybreaks, please read Comment #3.

thanks, 
-- stratus

I've got the same problem on OS X; the fix reported by gustavorfranco works.

When I search for "dev_appserver.py" I only find the files supplied with the 
SDK.
Within the jaiku project, I can't find the externals mentioned by 
gustavorfranco.

Maybe I'm just being dense (yes, that's probably it), but a more explicit 
explanation
would be very helpful. 

thelevybreaks, don't you have a .google_appengine subdirectory into your 
jaikuengine
svn checkout?

-- stratus

Yes, I was being dense. I had Show Hidden Files toggled off in Nautilus. 

I'm not sure how roundabout adding a patch to fix this issue would have to be, 
we either need to restructure the 
build system or monkeypatch that file, i'd prefer not to do the latter but the 
former may make installation issues 
a bit more straightforward as well

Added a monkey patch to resolve this issue in r23