#31327: Deprecate providing_args argument from Signal
------------------------------------------------+------------------------
Reporter: Jon Dufresne | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Utilities | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
The argument is and always has been purely documentational. It provides no
functionality or checking. Therefore, these values are stored in memory
for no real use.
Documentation can be handled just as easily by a code comment or real
documentation articles.
On a more practical level, I rarely signals, so I recently had to look up
their interface. Seeing this `providing_args` argument required me to
think about how to best use it, only to realize it actually goes unused.
We can remove this cognitive distraction from the docs.
It has caused other small confusion in the past: #19579.
--
Ticket URL: <https://code.djangoproject.com/ticket/31327>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.1a7085b3cceb96f483678a1faa52fcf7%40djangoproject.com.
