#19579: Docs aren't clear on purpose of signals' "providing_args"
-------------------------------+------------------------------------
Reporter: anonymous | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.4
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by akaariai):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
We could likely check that the args in send() match providing_args, but
that might be somewhat costly. Maybe if settings.DEBUG = True then we do
the checking, otherwise not? I think we could arrange the code in such a
way that there is zero overhead when settings.DEBUG = False.
Marking as accepted for the documentation part.
--
Ticket URL: <https://code.djangoproject.com/ticket/19579#comment:1>
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.
