mirror of
https://github.com/django/django.git
synced 2025-09-26 12:09:19 +00:00
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.
This commit is contained in:
parent
319b7112d8
commit
b28c60529b
4 changed files with 36 additions and 6 deletions
|
@ -845,7 +845,7 @@ types.
|
|||
|
||||
.. attribute:: base_field
|
||||
|
||||
The model field to use.
|
||||
The model field class to use.
|
||||
|
||||
.. attribute:: range_type
|
||||
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue