#26778: ModelSignal.connect() does not work when 'weak' is set to False and
receiver is a local function
-------------------------------------+-------------------------------------
Reporter: laevilgenius | Owner: timgraham
Type: Bug | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"91d754eb2a109e5d15bdbedb3b945abc32425250" 91d754e]:
{{{
#!CommitTicketReference repository=""
revision="91d754eb2a109e5d15bdbedb3b945abc32425250"
[1.10.x] Fixed #26778 -- Fixed ModelSignal.connect() weak argument.
Backport of 9bf8d50a678463a5a3cd52f10c830fe0ca65d2c6 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26778#comment:4>
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/070.9db9a1c2c0d8277018a9baed57040f89%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
