#28978: m2m_changed signal's "model" argument is acting wierd
-------------------------------------+-------------------------------------
Reporter: Dev Aggarwal | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Dev Aggarwal):
Replying to [comment:2 Ramiro Morales]:
> We'll need more information to tell if there is some Django issue worth
investigating here:
>
> What do you expect to see in that ''model'' parameter?
>
> And a description of the M2M model setup would be great. Bonus points if
you can provide a minimal project showing the issue.
Thanks for the reply.
I figured out what the problem was. I thought that model was an instance
but it was the actual class of my model
doing this produced the required behavior :)
{{{
>> model == models.Question
True
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28978#comment:3>
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/064.c8d3073a41752d8cbb21f587f5c68b91%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
