1293 sections across all versions Narrow to Django 6.0 (current) →
Release notes Django 5.2.12 release notes
The URLField form field’s to_python() method used urlsplit() to determine whether to prepend a URL scheme to the submitted value. On Windows, urlsplit() performs NFKC normalization, which can be disproportionately slow for large inputs containing certain characters.
Release notes Django 6.0.3 release notes
The URLField form field’s to_python() method used urlsplit() to determine whether to prepend a URL scheme to the submitted value. On Windows, urlsplit() performs NFKC normalization, which can be disproportionately slow for large inputs containing certain characters.
Release notes Django 1.1.4 release notes
Django includes a CSRF-protection mechanism, which makes use of a token inserted into outgoing forms. Middleware then checks for the token’s presence on form submission, and validates it.
Release notes Django 1.2.5 release notes
Django includes a CSRF-protection mechanism, which makes use of a token inserted into outgoing forms. Middleware then checks for the token’s presence on form submission, and validates it.
Release notes Django 1.7 release notes
The required attribute for each individual field will be respected, and a new incomplete validation error will be raised when any required fields are empty. The clean() method on a form no longer needs to return self.cleaned_data.
Release notes Django 1.9 release notes
The UTC offset is stored on a data attribute of the <body> tag. CommaSeparatedIntegerField validation has been refined to forbid values like ',', ',1', and '1,,2'. Form initialization was moved from the ProcessFormView.get() method to the new FormMixin.get_context_data() method.
Release notes Django 1.1.4 release notes Backwards incompatible changes
Django includes a CSRF-protection mechanism, which makes use of a token inserted into outgoing forms. Middleware then checks for the token’s presence on form submission, and validates it.
Release notes Django 1.2.5 release notes Backwards incompatible changes
Django includes a CSRF-protection mechanism, which makes use of a token inserted into outgoing forms. Middleware then checks for the token’s presence on form submission, and validates it.
Release notes Django 1.7 release notes What’s new in Django 1.7Minor features
The required attribute for each individual field will be respected, and a new incomplete validation error will be raised when any required fields are empty. The clean() method on a form no longer needs to return self.cleaned_data.
Release notes Django 1.9 release notes Features deprecated in 1.9
The UTC offset is stored on a data attribute of the <body> tag. CommaSeparatedIntegerField validation has been refined to forbid values like ',', ',1', and '1,,2'. Form initialization was moved from the ProcessFormView.get() method to the new FormMixin.get_context_data() method.
Release notes Django 1.3 release notes
In Django 1.3 FormSet creation behavior is modified slightly. Historically the class didn’t make a distinction between not being passed data and being passed empty dictionary. This was inconsistent with behavior in other parts of the framework.
Release notes Django 1.7 release notes
… an unauthorized or unauthenticated user directly to the login view, without HTTP redirection. In Django 1.7, this behavior changed to conform to a more traditional workflow where any unauthorized request to an admin page will be redirected (by HTTP status …
Release notes Django 1.3 release notes Backwards-incompatible changes in 1.3
In Django 1.3 FormSet creation behavior is modified slightly. Historically the class didn’t make a distinction between not being passed data and being passed empty dictionary. This was inconsistent with behavior in other parts of the framework.
Release notes Django 1.7 release notes Backwards incompatible changes in 1.7
… an unauthorized or unauthenticated user directly to the login view, without HTTP redirection. In Django 1.7, this behavior changed to conform to a more traditional workflow where any unauthorized request to an admin page will be redirected (by HTTP status …
Release notes Django 1.11.2 release notes
Relaxed the validation added in Django 1.11 of the fields in the defaults argument of QuerySet.get_or_create() and update_or_create() to reallow settable model properties (#28222). Fixed MultipleObjectMixin.paginate_queryset() crash on Python 2 if the InvalidPage message contains non-ASCII (#28204).
Release notes Django 1.4 release notes
… contrib.auth password reset hash Consequences: Password reset links from before the upgrade will not work. Time period: Defined by PASSWORD_RESET_TIMEOUT_DAYS. Form-related hashes: these have a much shorter lifetime and are relevant only for the short window where a user might …
Release notes Django 2.0 release notes
Django favors callable references since they provide better performance and debugging experience. RedirectView no longer silences NoReverseMatch if the pattern_name doesn’t exist. When USE_L10N is off, FloatField and DecimalField now respect DECIMAL_SEPARATOR and THOUSAND_SEPARATOR during validation.
Release notes Django 4.1 release notes
The type="text/css" attribute is no longer included in <link> tags for CSS form media. formset:added and formset:removed JavaScript events are now pure JavaScript events and don’t depend on jQuery. See Inline form events for more details on the change.
Release notes Django 6.1 release notes
This should improve performance for models with many foreign key fields. The delete_confirmation_max_display option allows customizing how many objects are displayed on admin delete confirmation pages and inline protected deletion errors before the remainder is truncated.
Release notes Django 1.11.2 release notes
Relaxed the validation added in Django 1.11 of the fields in the defaults argument of QuerySet.get_or_create() and update_or_create() to reallow settable model properties (#28222). Fixed MultipleObjectMixin.paginate_queryset() crash on Python 2 if the InvalidPage message contains non-ASCII (#28204).