Release notes Django 4.1 release notes Features deprecated in 4.1

Use errors=[] instead. django.contrib.sessions.serializers.PickleSerializer is deprecated due to the risk of remote code execution. The usage of QuerySet.iterator() on a queryset that prefetches related objects without providing the chunk_size argument is deprecated. In older versions, no prefetching was done.

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

Other new features and changes introduced since Django 1.0 include: The CSRF protection middleware has been split into two classes – CsrfViewMiddleware checks incoming requests, and CsrfResponseMiddleware processes outgoing responses.

Release notes Django 1.9 release notes

django.core.cache.get_cache is removed. django.db.models.loading is removed. Passing callable arguments to querysets is no longer possible. BaseCommand.requires_model_validation is removed in favor of requires_system_checks. Admin validators is replaced by admin checks. The ModelAdmin.validator_class and default_validator_class attributes are removed. ModelAdmin.validate() is removed.

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 Django 3.0 release notes What’s new in Django 3.0Minor features

Added hash database functions MD5, SHA1, SHA224, SHA256, SHA384, and SHA512. Added the Sign database function. The new is_dst parameter of the Trunc database functions determines the treatment of nonexistent and ambiguous datetimes.

How-to How to use Django’s CSRF protection Using CSRF protection with AJAX

If you activate CSRF_USE_SESSIONS or CSRF_COOKIE_HTTPONLY, you must include the CSRF token in your HTML and read the token from the DOM with JavaScript:

Release notes Archive of security issues Issues under Django’s security process

Data leakage via querystring manipulation in admin. Full description

Release notes Django 1.1.3 release notes Backwards incompatible changes

The Django administrative interface, django.contrib.admin, supports filtering of displayed lists of objects by fields on the corresponding models, including across database-level relationships.

Release notes Django 1.2.4 release notes Backwards incompatible changes

The Django administrative interface, django.contrib.admin, supports filtering of displayed lists of objects by fields on the corresponding models, including across database-level relationships.

Release notes Django 1.4 release notes Backwards incompatible changes in 1.4

Django’s comments has historically supported excluding the comments of a special user group, but we’ve never documented the feature properly and didn’t enforce the exclusion in other parts of the app such as the template tags.

Release notes Django 1.8 release notes Features deprecated in 1.8

The django.db.models.sql.aggregates and django.contrib.gis.db.models.sql.aggregates modules (both private API), have been deprecated as django.db.models.aggregates and django.contrib.gis.db.models.aggregates are now also responsible for SQL generation. The old modules will be removed in Django 1.10.

Release notes Django 1.4.11 release notes

Django’s URL handling is based on a mapping of regex patterns (representing the URLs) to callable views, and Django’s own processing consists of matching a requested URL against those patterns to determine the appropriate view to invoke.

Release notes Django 1.5.6 release notes

Django’s URL handling is based on a mapping of regex patterns (representing the URLs) to callable views, and Django’s own processing consists of matching a requested URL against those patterns to determine the appropriate view to invoke.

Release notes Django 1.6.3 release notes

Django’s URL handling is based on a mapping of regex patterns (representing the URLs) to callable views, and Django’s own processing consists of matching a requested URL against those patterns to determine the appropriate view to invoke.