> Adrian Holovaty <[email protected]> Jan 13 12:07PM -0600 > The ultimate solution is: don't use model forms. I never use them for > anything, precisely because of things like this, where the framework > is trying to do too much behind the scenes. It's too magical for my > tastes, and while I understand why we added it to the framework, I see > it as a crutch for lazy developers. C'mon, it's not a lot of work to > create a "normal" (non-model) form class and pass its cleaned data to > a model's save() method. > > End rant. :-)
<delurk> I pretty much agree with Adrian. I use ModelForms when I'm grinding out stuff fast, but for real, detail work, I rely on normal forms.Forms. My reasons match Adrian's reasons. I use them as a crutch, but the magic can hurt at the worst time. So when I have time, I refactor to make thing simpler and less atomic. I leave all the magic stuff to smart people. ;) </delurk> -- 'Knowledge is Power' Daniel Greenfeld http://pydanny.blogspot.com -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
