#24205: Remove or deprecate weak parameter to Signal.disconnect()
------------------------------------------------+------------------------
Reporter: timgraham | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
The parameter has no effect. I'm in favor of simply removing it and
documenting it as a backwards incompatible change. A deprecation seems to
simply add overhead. A library that attempts to support multiple versions
of Django can remove the parameter without any backwards compatibility
concerns. Any opposition to that?
--
Ticket URL: <https://code.djangoproject.com/ticket/24205>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.dbf5d0f7ea7a4b04a9d324b1b5c9a0fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
