yes, it is "Lazy" in the "not evaluated until asked for sense" but
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/
python2.5/django/core/context_processors.py", line 20, in auth
if hasattr(request, 'user'):
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/
LazyUser is lazy and works fine. It's only triggered because of the
messages part of the processor so that's the root of the problem
(which is currently being talked about in another thread)
On Oct 29, 4:51 am, bo <[EMAIL PROTECTED]> wrote:
> well, not exactly.
>
> the "LazyUser" is the thing
well, not exactly.
the "LazyUser" is the thing that is not so lazy (yes i agree that the
messages are not lazy either), the Session is hit on the get_user
statement in auth() before the messages are even considered (see the
back trace).
The idea i am proposing is to make that entire
On Mon, Oct 27, 2008 at 8:59 PM, bo <[EMAIL PROTECTED]> wrote:
> thus i do not need
> django.core.context_processors.auth) but "contrib.admin" screams if it
> is not included.
I don't want to steer the thread off-topic, but I've been bitten by
this as well. My specific usecase is a project in
This is exactly why my patch in the session messages ticket [1] makes
the messages lazy.
[1] http://code.djangoproject.com/ticket/4604
On Oct 28, 1:59 pm, bo <[EMAIL PROTECTED]> wrote:
> Actually i've found that the issue lies with the
> TEMPLATE_CONTEXT_PROCESSORS
>
>
Actually i've found that the issue lies with the
TEMPLATE_CONTEXT_PROCESSORS
django.core.context_processors.auth
which does the get_and_delete messages bit ..
so i guess that is the proper behavior.
Sad to say that although my app can work around that issue (by using a
different messages
I'm not sure if this is 'supposed' to be the case or not so i'll ask
i think i've seen a similar post like this before, but either a) i'm
bad a search for it or b) it was only slightly related
--- the issue ---
using RequestContext(request, {}) + Auth.middleware always seems to
access the
