From c6d5f743713529537b3f5cbdf146c6222a635d5a Mon Sep 17 00:00:00 2001 From: aruseni Date: Sun, 9 Nov 2014 22:31:53 +0100 Subject: [PATCH] [1.7.x] Fixed a typo in 1.6 release notes. Backport of 006451f894 from master --- docs/releases/1.6.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/releases/1.6.txt b/docs/releases/1.6.txt index 41a9ae34a6..8737d08571 100644 --- a/docs/releases/1.6.txt +++ b/docs/releases/1.6.txt @@ -1183,7 +1183,7 @@ create a ``ModelForm`` that uses all fields for a model. For this reason, if you use these views for editing models, you must also supply the ``fields`` attribute (new in Django 1.6), which is a list of model fields and works in the same way as the :class:`~django.forms.ModelForm` -``Meta.fields`` attribute. Alternatively, you can set set the ``form_class`` +``Meta.fields`` attribute. Alternatively, you can set the ``form_class`` attribute to a ``ModelForm`` that explicitly defines the fields to be used. Defining an ``UpdateView`` or ``CreateView`` subclass to be used with a model but without an explicit list of fields is deprecated.