Hi all,
I'm working on a project which uses pyamf and produces the following
exception during login:

AttributeError: 'LazyModule' object has no attribute 'Manager'

However debugging this has been difficult. The error shows up with the
following setup:
 - django 1.0
 - pyamf 0.3.1
 - apache 2.2.9 (prefork)
 - mod_wsgi 2.3 (embedded)
 - SESSION_ENGINE = 'django.contrib.sessions.backends.cache'

We'll get the AttributeError about 5 times before that works, and then
finally the authentication call will go through. (I mention that it is
5 times because we're using the default StartServers count, and I
think that's why it's changing.) We continue to have problems after
that but I haven't diagnosed them much (and figure they'll be solved
by fixing the issue above).

Using the default db SESSION_ENGINE apparently solves all of these
problems. So does using runserver (with the caching session engine),
and with StartServers 1 and ServerLimit 1 things go fine (although the
performance is horrible), which indicates that file permissions, etc
are okay.

Finally, although LazyModule comes from pyamf, since this shows up
only when we're using the caching session engine I thought I'd check
in here before asking on the pyamf list.

So... has anybody seen this before?

Thanks!
 -rob
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to