cleverking / jaikuengine

Automatically exported from code.google.com/p/jaikuengine
0 stars 0 forks source link

ImportError: No module named django (and django is properly installed on this machine) #6

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
[Note: this is for reporting issues on the JaikuEngine open source project.
if you are reporting an issue with the jaiku.com service, please send it to
support@jaiku.com]

What steps will reproduce the problem?
1. Starting server with manage.py

What is the expected output? What do you see instead?

I get the purple error screen with an ImportError: No module named django.
I have Django on this machine and can run other django applications.  

What version of the product are you using? On what operating system?

March 14th build, on Ubuntu 8.04

Ubuntu

Please provide any additional information below.

Original issue reported on code.google.com by thelevyb...@gmail.com on 14 Mar 2009 at 7:12

GoogleCodeExporter commented 8 years ago
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)

Original comment by mika.rae...@gmail.com on 14 Mar 2009 at 9:26

GoogleCodeExporter commented 8 years ago
Issue 14 has been merged into this issue.

Original comment by tony.t.t...@gmail.com on 14 Mar 2009 at 6:03

GoogleCodeExporter commented 8 years ago
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

Original comment by gustavor...@gmail.com on 14 Mar 2009 at 7:02

GoogleCodeExporter commented 8 years ago
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. 

Original comment by thelevyb...@gmail.com on 14 Mar 2009 at 11:08

GoogleCodeExporter commented 8 years ago
thelevybreaks, please read Comment #3.

thanks, 
-- stratus

Original comment by gustavor...@gmail.com on 14 Mar 2009 at 11:14

GoogleCodeExporter commented 8 years ago
I've got the same problem on OS X; the fix reported by gustavorfranco works.

Original comment by jamezpol...@gmail.com on 16 Mar 2009 at 9:05

GoogleCodeExporter commented 8 years ago
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. 

Original comment by thelevyb...@gmail.com on 17 Mar 2009 at 8:33

GoogleCodeExporter commented 8 years ago
thelevybreaks, don't you have a .google_appengine subdirectory into your 
jaikuengine
svn checkout?

-- stratus

Original comment by gustavor...@gmail.com on 17 Mar 2009 at 8:46

GoogleCodeExporter commented 8 years ago
Yes, I was being dense. I had Show Hidden Files toggled off in Nautilus. 

Original comment by thelevyb...@gmail.com on 17 Mar 2009 at 9:02

GoogleCodeExporter commented 8 years ago
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

Original comment by andyster on 19 Mar 2009 at 9:16

GoogleCodeExporter commented 8 years ago
Added a monkey patch to resolve this issue in r23

Original comment by andyster on 24 Mar 2009 at 9:05