Hi, I agree. I'm just not so sure about the is_valid_user method, people will have to start checking for this method instead of checking for an existent user.
I can't imagine someone needing to authenticate a non-active user, and even if someone do, he'll be able to do it manually, or passing "is_active=False" to the authenticate method. In other hand, maybe (note: maybe) this can break projects that don't check for this flag. So, I can see two paths: - change this behaviour; - make a note in the docs that inactive users can authenticate. Best regards. Enrico --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
