#11400: Add fail_silently parameter to User.email_user
-------------------------------------+-------------------------------------
Reporter: Jug_ | Owner: nobody
Type: New feature | Status: new
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: email user | Triage Stage: Accepted
fail_silently | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 1 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by vanschelven):
Just weighing in on a ticket that seems to be living in limbo for three
years at this point:
This should either be 'design decision needed', or be quickly resolved,
since it seems rather trivial to me. What's needed to move this forward?
Personally, I don't think passing ```**kwargs``` around is the pinnacle of
elegance. Are there more ```kwargs``` that we're interested in, or is it
really just ```fail_silently```?
As a final thought, if we consider this a desirable feature, maybe
fail_silently should be customizable in more cases. Specifically, it's not
easy to customize the ```password_reset``` view to have a different value
for fail_silently without subclassing and completely copy/pasting
```PasswordResetForm```. Maybe that's a separate ticket?
--
Ticket URL: <https://code.djangoproject.com/ticket/11400#comment:8>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
