#16797: active_login_required
-------------------------------------+-------------------------------------
Reporter: wim@… | Owner: nobody
Type: New | Status: closed
feature | Component: contrib.auth
Milestone: | Severity: Normal
Version: 1.3 | Keywords:
Resolution: wontfix | Has patch: 1
Triage Stage: Design | Needs tests: 1
decision needed | Easy pickings: 0
Needs documentation: 1 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by jacob):
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for the suggestion, Wim, but I think this is something that
shouldn't go into Django. Every site is going to have their own slightly
different auth needs, and that's the purpose of the generic
`user_passes_test` meta-decorator. Including each and every slightly
different permutation of auth logic in Django is a path that leads towards
spaghetti code. Further, this is trivial to accomplish in your own code,
so there isn't a much impetus to include it in Django.
Thanks again!
--
Ticket URL: <https://code.djangoproject.com/ticket/16797#comment:7>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
