689 sections across all versions Narrow to Django 6.0 (current) →
Release notes Django 5.0 release notes Features deprecated in 5.0
The DjangoDivFormRenderer and Jinja2DivFormRenderer transitional form renderers are deprecated. Passing positional arguments name and violation_error_message to BaseConstraint is deprecated in favor of keyword-only arguments. request is added to the signature of ModelAdmin.lookup_allowed().
Release notes Django 1.10.6 release notes
Fixed ClearableFileInput’s “Clear” checkbox on model form fields where the model field has a default (#27805). Fixed RequestDataTooBig and TooManyFieldsSent exceptions crashing rather than generating a bad request response (#27820).
Release notes Django 1.6 release notes Features deprecated in 1.6
If you defined your own form widgets and defined the _has_changed method on a widget, you should now define this method on the form field itself.
Release notes Django 1.7 release notes What’s new in Django 1.7Minor features
Calls to WizardView.done() now include a form_dict to allow easier access to forms by their step name.
Release notes Django 5.2 release notes What’s new in Django 5.2Minor features
The new ColorInput form widget is for entering a color in rrggbb hexadecimal format and renders as <input type="color" ...>. Some browsers support a visual color picker interface for this input type.
Release notes Django 1.11 release notes What’s new in Django 1.11
To ease customizing widgets, form widget rendering is now done using the template system rather than in Python. See The form rendering API. You may need to adjust any custom widgets that you’ve written for a few backwards incompatible changes.
Release notes Django 1.3 release notes Backwards-incompatible changes in 1.3
The PasswordInput form widget, intended for use with form fields which represent passwords, accepts a boolean keyword argument render_value indicating whether to send its data back to the browser when displaying a submitted form with errors.
Release notes Django 1.3.6 release notes
Previous versions of Django did not validate or limit the form-count data provided by the client in a formset’s management form, making it possible to exhaust a server’s available memory by forcing it to create very large numbers of forms.
Release notes Django 1.4.4 release notes
Previous versions of Django did not validate or limit the form-count data provided by the client in a formset’s management form, making it possible to exhaust a server’s available memory by forcing it to create very large numbers of forms.
Release notes Django 2.2 release notes Features deprecated in 2.2
To improve readability, the UUIDField form field now displays values with dashes, e.g. 550e8400-e29b-41d4-a716-446655440000 instead of 550e8400e29b41d4a716446655440000. On SQLite, PositiveIntegerField and PositiveSmallIntegerField now include a check constraint to prevent negative values in the database.
Release notes Porting your apps from Django 0.96 to 1.0 Common changesModels
Rename your maxlength argument to max_length (this was changed to be consistent with form fields):
Release notes Django 1.2 release notes What’s new in Django 1.2
Django’s internationalization framework has been expanded with locale-aware formatting and form processing. That means, if enabled, dates and numbers on templates will be displayed using the format specified for the current locale.
Release notes Django 1.3 release notes Backwards-incompatible changes in 1.3
Django 1.3 now includes a ClearableFileInput form widget in addition to FileInput.
Release notes Django 2.1 release notes Backwards incompatible changes in 2.1Considerations for the new model “view” permission
If you have a custom permission with a codename of the form view_<modelname>, the new view permission handling in the admin will allow view access to the changelist and detail pages for those models.
Release notes Django 4.0.1 release notes
Fixed a regression in Django 4.0 that caused a crash of assertFormsetError() on a formset named form (#33346). Fixed a bug in Django 4.0 that caused a crash on booleans with the RedisCache backend (#33361).
Release notes Django 4.2 release notes What’s new in Django 4.2Minor features
ModelForm now accepts the new Meta option formfield_callback to customize form fields. modelform_factory() now respects the formfield_callback attribute of the form’s Meta.
Release notes Django 1.0 release notes What’s new in Django 1.0
… definitions are now completely decoupled from model definitions (no more class Admin declaration in models!), rewritten to use Django’s new form-handling library (introduced in the 0.96 release as django.newforms, and now available as simply django.forms) and redesigned with extensibility and …
Release notes Django 1.0 release notes What’s new in Django 1.0
A project over a year in the making, this adds world-class GIS (Geographic Information Systems) support to Django, in the form of a contrib application.
Release notes Django 1.0 release notes What’s new in Django 1.0
… were scheduled for removal prior to the 1.0 release, are no longer present in Django. These include imports of the form library from django.newforms (now located simply at django.forms), the form_for_model and form_for_instance helper functions (which have been replaced by …
Release notes Porting your apps from Django 0.96 to 1.0 Less-common changesHTTP request/response objects
… both GET and POST data were directly available on the HttpRequest object (e.g., you could check for a piece of form data by using if 'some_form_key' in request or by reading request['some_form_key']. This is no longer supported; if you need …