From b28c60529bfa94702a50990fc2d40faa837fca9c Mon Sep 17 00:00:00 2001 From: anna Date: Sun, 3 Apr 2016 12:39:18 +0200 Subject: Fixed #26101 -- Allowed introspection of base_field.model in RangeField Used the same test and fix as in #25867. This required initializing base_field in RangeField.__init__, not when setting the attribute. --- docs/ref/contrib/postgres/fields.txt | 2 +- docs/releases/1.10.txt | 6 ++++++ 2 files changed, 7 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/ref/contrib/postgres/fields.txt b/docs/ref/contrib/postgres/fields.txt index 0c89a22749..b7938dcb2f 100644 --- a/docs/ref/contrib/postgres/fields.txt +++ b/docs/ref/contrib/postgres/fields.txt @@ -845,7 +845,7 @@ types. .. attribute:: base_field - The model field to use. + The model field class to use. .. attribute:: range_type diff --git a/docs/releases/1.10.txt b/docs/releases/1.10.txt index c8696f8d85..1ad08f10c2 100644 --- a/docs/releases/1.10.txt +++ b/docs/releases/1.10.txt @@ -705,6 +705,12 @@ Miscellaneous * :func:`django.views.i18n.set_language` may now return a 204 status code for AJAX requests. +* The ``base_field`` attribute of + :class:`~django.contrib.postgres.fields.RangeField` is now a type of field, + not an instance of a field. If you have created a custom subclass of + :class:`~django.contrib.postgres.fields.RangeField`, you should change the + ``base_field`` attribute. + .. _deprecated-features-1.10: Features deprecated in 1.10 -- cgit v1.3