There is a case in favour of the need for this: if an application uses a
custom user model, there can be additional properties and methods added to
it, and it makes sense for the AnonymousUser to be able to mirror those
properties (even if they are falsey). For the sake of coherence, I believe
it makes sense to have the ability to specify a custom AnonymousUser
class, just as the AbstractUser.
--
Ticket URL: <https://code.djangoproject.com/ticket/30012>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* stage: Unreviewed => Accepted
Comment:
That makes sense to me.
Did you have any implementation in mind? I was thinking a class attribute
on `AbstractUser` could do?
--
Ticket URL: <https://code.djangoproject.com/ticket/30012#comment:1>
* status: new => closed
* resolution: => duplicate
Comment:
Actually this is a duplicate of #20313.
--
Ticket URL: <https://code.djangoproject.com/ticket/30012#comment:2>