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.8 release notes Features deprecated in 1.8

The return type of get_template() has changed in Django 1.8: instead of a django.template.Template, it returns a Template instance whose exact type depends on which backend loaded it.

Release notes Django 2.0 release notes Backwards incompatible changes in 2.0

This section describes changes that may be needed in third-party database backends. The DatabaseOperations.datetime_cast_date_sql(), datetime_cast_time_sql(), datetime_trunc_sql(), datetime_extract_sql(), and date_interval_sql() methods now return only the SQL to perform the operation instead of SQL and a list of parameters.

Release notes Django 2.0.1 release notes

Fixed a regression in Django 1.11 that added newlines between MultiWidget’s subwidgets (#28890). Fixed incorrect class-based model index name generation for models with quoted db_table (#28876). Fixed incorrect foreign key constraint name for models with quoted db_table (#28876).

Release notes Django 2.2.8 release notes

Fixed a data loss possibility in the admin changelist view when a custom formset’s prefix contains regular expression special characters, e.g. '$' (#31031).

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

Django now supports a fully asynchronous request path, including: Asynchronous views Asynchronous middleware Asynchronous tests and test client To get started with async views, you need to declare a view using async def: All asynchronous features are supported whether you …

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

New QuerySet.contains(obj) method returns whether the queryset contains the given object. This tries to perform the query in the simplest and fastest way possible.

Release notes Django 4.2.6 release notes

Fixed a regression in Django 4.2.5 where overriding the deprecated DEFAULT_FILE_STORAGE and STATICFILES_STORAGE settings in tests caused the main STORAGES to mutate (#34821).

Release notes Django 5.1.2 release notes

Fixed a regression in Django 5.1 that caused a crash when using the PostgreSQL lookup trigram_similar on output fields from Concat (#35732).

Release notes Django 1.10 release notes Features deprecated in 1.10

The repr() of a QuerySet is wrapped in <QuerySet > to disambiguate it from a plain list when debugging. utils.version.get_version() returns PEP 440 compliant release candidate versions (e.g. ‘1.10rc1’ instead of ‘1.10c1’).

Release notes Django 1.11.3 release notes

Removed an incorrect deprecation warning about a missing renderer argument if a Widget.render() method accepts **kwargs (#28265). Fixed a regression causing Model.__init__() to crash if a field has an instance only descriptor (#28269).

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

Django 1.4 also includes several smaller improvements worth noting: A more usable stacktrace in the technical 500 page. Frames in the stack trace that reference Django’s framework code are dimmed out, while frames in application code are slightly emphasized.

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

The <label> and <input> tags rendered by RadioSelect and CheckboxSelectMultiple when looping over the radio buttons or checkboxes now include for and id attributes, respectively. Each radio button or checkbox includes an id_for_label attribute to output the element’s ID.

Release notes Django 1.8 release notes

These features have reached the end of their deprecation cycle and are removed in Django 1.8. See Features deprecated in 1.6 for details, including how to remove usage of these features. django.contrib.comments is removed.

Release notes Django 2.0 release notes Features deprecated in 2.0

The SessionAuthenticationMiddleware class is removed. It provided no functionality since session authentication is unconditionally enabled in Django 1.10. The default HTTP error handlers (handler404, etc.) are now callables instead of dotted Python path strings.

Reference Settings Sessions

Default: 'default' If you’re using cache-based session storage, this selects the cache to use.

Topic guide Django’s cache framework Setting up the cache

Here’s an example configuration for a redis based backend that selects database 10 (by default Redis ships with 16 logical databases), and sets a custom connection pool class (redis.ConnectionPool is used by default):

Topic guide Making queries Retrieving objectsRetrieving specific objects with filters

Each time you refine a QuerySet, you get a brand-new QuerySet that is in no way bound to the previous QuerySet. Each refinement creates a separate and distinct QuerySet that can be stored, used and reused.

Internals Django’s security policies Reporting security issuesReporting guidelines

Reports based on a failure to sanitize user input are not valid security vulnerabilities. It is the developer’s responsibility to properly handle user input. This principle is explained in our security documentation.

Topic guide Time zones Concepts

The current time zone is the equivalent of the current locale for translations. However, there’s no equivalent of the Accept-Language HTTP header that Django could use to determine the user’s time zone automatically. Instead, Django provides time zone selection functions.