On Sat, 2008-12-13 at 05:07 -0800, Vladimir Kirillov wrote: > using django-1.0.2 with apache-1.3 (OpenBSD), python-2.4, fastcgi and > py-flup-1.0 from yesterday's mercurial tip
By the way, for the future, you'll probably want to find a way to work out what the real subversion revision is that your checkout corresponds to. I don't know where you are doing the mercurial checkout from, but the canonical reference is always the subversion repository. If you are ever reporting a bug that might have been introduced recently, it will be very helpful, practically compulsory, to know which subversion revisions are involved. > throws these logs into > error-log and 500 to any requests: > apache error logs: > Traceback (most recent call last): > File "../lib/flup/server/fcgi_base.py", line 558, in run > File "../lib/flup/server/fcgi_base.py", line 1116, in handler > File "../lib/django/core/handlers/wsgi.py", line 228, in __call__ > File "../lib/django/core/handlers/base.py", line 40, in > load_middleware > ImproperlyConfigured: Error importing middleware > django.middleware.common: "No module named common" > > (sometimes can be caused on other modules) It's possible your Python path is not set correctly for the process that is running flup, but that seems unlikely, since importing wsgi.py and base.py requires importing things from other places in Django. My best guess would be that permissions are somehow set differently on some of the directories, so they cannot be read by the process and user running flup. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
