I admit, I have my own truncate filter on my website so why should I care
about bringing the truncate filter up? Heck, I've got a pretty big patchset
of features I need but "just wont be accepted".
However, feedback on an application can come from anywhere. When someone
just discovers a framework,
There is already a ticket for this request:
http://code.djangoproject.com/ticket/12090
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group,
I can see some benefit in consistency here but what do you do about
saving the current object?
This is a problem in general with any actions performed on the same
screen a change form.
1. User enters the object detail view
2. User changes a field
3. User selects an action.
Does the action apply
