#13087: m2m_changed fires before a clear but after add/remove
---------------------------------------------+------------------------------
Reporter: rcatherman | Owner: nobody
Status: new | Milestone: 1.2
Component: Uncategorized | Version: 1.2-beta
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by russellm):
* needs_better_patch: => 0
* needs_docs: => 0
* stage: Unreviewed => Design decision needed
* needs_tests: => 0
* milestone: => 1.2
Comment:
This certainly needs to be decided before 1.2. The current behaviour is
deliberate, and documented as implemented; I need to think about this
(preferably with a clear head) to determine if the current behavior is the
most desirable.
--
Ticket URL: <http://code.djangoproject.com/ticket/13087#comment:1>
Django <http://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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
