#29381: Move some parts of `django.contrib.auth.models` to
`django.contrib.auth.base_user` for reusability
-------------------------------+--------------------------------------
Reporter: Sagar Chalise | Owner: nobody
Type: New feature | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Sagar Chalise):
* needs_better_patch: 1 => 0
* stage: Accepted => Unreviewed
* needs_tests: 1 => 0
* needs_docs: 1 => 0
Comment:
Yes, when I avoid `contrib.auth` I need to rewrite the part I moved to be
used by my custom authentication middleware. I think it makes sense to
provide the interface similar to `AbstractBaseUser` for maybe
`AbstractAnonymousUser` just for code reusabilty. Obviously this can be
thought of for other stuffs such as backends as well where there is no
need of `Permission` model.
--
Ticket URL: <https://code.djangoproject.com/ticket/29381#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.c67e46cb939aae6d00d7abf8d76ebdf9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
