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).
476 sections across all versions Narrow to Django 6.0 (current) →
Release notes Django 1.10 release notes
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
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
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
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.
Release notes Django 6.1 release notes
The iexact=None lookup on JSONField key transforms now matches JSON null, to match the behavior of exact=None on key transforms. Previously, it was interpreted as an isnull lookup.
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
Default: 'default' If you’re using cache-based session storage, this selects the cache to use.
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 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), specifies a parser class (redis.connection.HiredisParser will be used by default if the hiredis-py package is installed), and sets a …
Topic guide Django’s cache framework
Here’s an example configuration for a pymemcache based backend that enables client pooling (which may improve performance by keeping clients connected), treats memcache/network errors as cache misses, and sets the TCP_NODELAY flag on the connection’s socket: Here’s an example configuration …
Topic guide Making queries
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.