On March 12, 2012, at 14:47 , Clay McClure wrote:
> On Thursday, February 23, 2012 10:41:36 AM UTC-5, Tom Evans wrote:
> there is also the possible source of confusion stemming from the fact that
> in template language we write:
>
> {% if user.is_authenticated %}
>
> but in Python we
On Thursday, February 23, 2012 10:41:36 AM UTC-5, Tom Evans wrote:
I don't like this function that much.
>
I share that sentiment. When it becomes possible to refactor auth.User, I
hope we'll be able to first deprecate and then remove
User.is_authenticated() and User.is_anonymous(). In addition
On 02/23/2012 09:42 AM, Luke Granger-Brown wrote:
> It does prove that they've authenticated, in that request.user will
> contain an AnonymousUser if they're not logged in, which overrides this
> method to always return False. If they are, then they'll get their
> actual user, which will return
Hi Tom,
On 02/23/2012 08:41 AM, Tom Evans wrote:
> I don't like this function that much. It doesn't actually check
> whether users are authenticated - which is to say, they have presented
> credentials which we have accepted and authorized them to use to the
> site. Instead it always returns
Hi all
I don't like this function that much. It doesn't actually check
whether users are authenticated - which is to say, they have presented
credentials which we have accepted and authorized them to use to the
site. Instead it always returns true. is_not_anonymous_user() may be a
better name.
