#6108: send all_objects_to_be_deleted in the pre_delete signal
----------------------------------------------------------+-----------------
Reporter: Gábor Farkas <ga...@nekomancer.net> | Owner:
nobody
Status: new | Milestone:
Component: Core framework | Version: SVN
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
----------------------------------------------------------+-----------------
Changes (by cgieringer):
* cc: cgieringer (added)
Comment:
Related: #6870. My two cents is that the signal's arguments are fine as-
is, it just needs to be called at an earlier point in time. Signals are
simple and elegant; they tell you just enough information to find the rest
of the information you might want. Adding the list of to-be-deleted
objects is unnecessary because a signal listener could create this list
without the signal including it.
--
Ticket URL: <http://code.djangoproject.com/ticket/6108#comment:11>
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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
