Release notes Django 2.1.15 release notes

… parent model but edit permissions to the inline model, would display a read-only view of the parent model but editable forms for the inline. Submitting these forms would not allow direct edits to the parent model, but would trigger the …

Release notes Django 2.1.2 release notes

Fixed a crash when a user with the view (but not change) permission made a POST request to an admin user change form (#29809).

Release notes Django 2.2.8 release notes

… parent model but edit permissions to the inline model, would display a read-only view of the parent model but editable forms for the inline. Submitting these forms would not allow direct edits to the parent model, but would trigger the …

Release notes Django 3.1 release notes What’s new in Django 3.1

Django now includes models.JSONField and forms.JSONField that can be used on all supported database backends. Both fields support the use of custom JSON encoders and decoders.

Release notes Django 3.1 release notes Backwards incompatible changes in 3.1

If you want to preserve the 30 character limit for first names, use a custom form: If you wish to keep this restriction in the admin when editing users, set UserAdmin.form to use this form:

Release notes Django 3.2 release notes What’s new in Django 3.2Minor features

The new absolute_max argument for formset_factory(), inlineformset_factory(), and modelformset_factory() allows customizing the maximum number of forms that can be instantiated when supplying POST data. See Limiting the maximum number of instantiated forms for more details.

Release notes Django 4.1 release notes What’s new in Django 4.1Minor features

The admin history view is now paginated. Related widget wrappers now have a link to object’s change form. The AdminSite.get_app_list() method now allows changing the order of apps and models on the admin index page.

Release notes Django 4.1 release notes What’s new in Django 4.1Minor features

A nested atomic block marked as durable in django.test.TestCase now raises a RuntimeError, the same as outside of tests. SimpleTestCase.assertFormError() and assertFormsetError() now support passing a form/formset object directly.

Release notes Django 5.1 release notes What’s new in Django 5.1Minor features

The new AdminUserCreationForm and the existing AdminPasswordChangeForm now support disabling password-based authentication by setting an unusable password on form save. This is now available in the admin when visiting the user creation and password change pages.

Release notes Django 5.2 release notes What’s new in Django 5.2

Django now supports specifying the following attributes to customize form rendering: BaseRenderer.bound_field_class at the project level, Form.bound_field_class at the form level, and Field.bound_field_class at the field level.

Release notes Django 5.2.2 release notes

Fixed a regression in Django 5.2 where admin’s filter_horizontal buttons lacked type="button", causing them to intercept form submission when pressing the Enter key (#36423).

Release notes Django 6.0 release notes

The DjangoDivFormRenderer and Jinja2DivFormRenderer transitional form renderers are removed. BaseDatabaseOperations.field_cast_sql() is removed. request is required in the signature of ModelAdmin.lookup_allowed() subclasses. Support for calling format_html() without passing args or kwargs is removed.

Release notes Django 6.0.1 release notes

Fixed a visual regression in Django 6.0 for admin form fields grouped under a <fieldset> in Safari (#36807). Fixed a crash in Django 6.0 caused by infinite recursion when calling repr() on an unevaluated django.utils.csp.LazyNonce instance (#36810).

Release notes Django 5.2.17 release notes

A maximum depth of 198 GEOMETRYCOLLECTIONs is now enforced for the well-known text (WKT) format, and a maximum number of 198 GEOMETRYCOLLECTIONs in total (breadth and depth) is enforced for well-known binary (WKB).

Release notes Django 6.0.8 release notes

A maximum depth of 198 GEOMETRYCOLLECTIONs is now enforced for the well-known text (WKT) format, and a maximum number of 198 GEOMETRYCOLLECTIONs in total (breadth and depth) is enforced for well-known binary (WKB).

Release notes Django 1.10 release notes

django.template.resolve_variable is removed. The following private APIs are removed from django.db.models.options.Options (Model._meta): get_field_by_name() get_all_field_names() get_fields_with_model() get_concrete_fields_with_model() get_m2m_with_model() get_all_related_objects() get_all_related_objects_with_model() get_all_related_many_to_many_objects() get_all_related_m2m_objects_with_model() The error_message argument of django.forms.RegexField is removed. The unordered_list filter no longer supports old style lists.

Release notes Django 1.7 release notes What’s new in Django 1.7Minor features

You can specify a descending ordering for a ModelAdmin.list_display value by prefixing the admin_order_field value with a hyphen. The ModelAdmin.get_changeform_initial_data() method may be overridden to define custom behavior for setting initial change form data.

Release notes Django 1.8 release notes Backwards incompatible changes in 1.8

This behavior could affect performance on IE7 and later. It was removed. URLField.to_python no longer adds a trailing slash to pathless URLs. The length template filter now returns 0 for an undefined variable, rather than an empty string.

Release notes Django 1.9 release notes What’s new in Django 1.9Minor features

Added jQuery events when an inline form is added or removed on the change form page. The time picker widget includes a ‘6 p.m’ option for consistency of having predefined options every 6 hours.

Release notes Django 3.1 release notes What’s new in Django 3.1Minor features

django.forms.DateTimeField now accepts dates in a subset of ISO 8601 datetime formats, including optional timezone, e.g. 2019-10-10T06:47, 2019-10-10T06:47:23+04:00, or 2019-10-10T06:47:23Z. The timezone will always be retained if provided, with timezone-aware datetimes being returned even when USE_TZ is False.