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 …

Release notes Django 1.1 release notes Backwards-incompatible changes in 1.1

In Django 1.1, BaseModelFormSet now calls ModelForm.save(). This is backwards-incompatible if you were modifying self.initial in a model formset’s __init__, or if you relied on the internal _total_form_count or _initial_form_count attributes of BaseFormSet. Those attributes are now public methods.

Release notes Django 1.1 release notes What’s new in Django 1.1New admin features

You can now make fields editable on the admin list views via the new list_editable admin option. These fields will show up as form widgets on the list pages, and can be edited and saved in bulk.

Release notes Django 1.10.7 release notes

Made admin’s RelatedFieldWidgetWrapper use the wrapped widget’s value_omitted_from_data() method (#27905). Fixed model form default fallback for SelectMultiple (#27993).

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

… protection against Cross-Site Request Forgery (CSRF) attacks. This type of attack occurs when a malicious website contains a link, a form button or some JavaScript that is intended to perform some action on your website, using the credentials of a …

Release notes

Django 1.2.1 was released almost immediately after 1.2.0 to correct two small bugs: one was in the documentation packaging script, the other was a bug that affected datetime form field widgets when localization was enabled.

Release notes Django 1.3 release notes Backwards-incompatible changes in 1.3

The django.contrib.auth.views.password_reset() view now accepts a from_email parameter, which is passed to the password_reset_form’s save() method as a keyword argument.