#4312: addition of defaults argument to newforms save()
----------------------------------+-----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: closed | Component: django.newforms
Version: SVN | Resolution: wontfix
Keywords: | Stage: Design decision
needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------------+-----------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => wontfix
Comment:
This functionality is already provided by the save(False) approach.
Attaching data to the form that isn't required for form presentation isn't
really a good idea, IMHO.
There is a problem with the save(False) approach when it comes to m2m
data. This problem is described in ticket #4001, but that problem is
solvable. The solution is to fix #4001, not to make form_for_model a
behemoth. Remember, form_for_model is a helper, not the end of the story
on newforms.
--
Ticket URL: <http://code.djangoproject.com/ticket/4312#comment:3>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
