Hey guys, I've ran into this problem before and it took me a while to figure out the issue. I've ran into it again while just playing around with a small app.
In the ModelForm you can define which fields to use. The documented example is here: https://docs.djangoproject.com/en/1.4/topics/forms/modelforms/#using-a-subset-of-fields-on-the-form In the 'exclude' attribute, they show the leading comma. In the 'fields' attribute, they don't. I haven't ran their exact example -- but something * very* similar and I get a weird error, unless I throw in the trailing comma after the final element of the tuple. I'm just wondering if anyone can verify that this is a bug with the documentation before I start the journey of searching through the existing tickets and filing one if it hasn't been reported. Thanks! -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/mDKpjP6Mw5IJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
