April 1, 2015

Welcome to Django 1.8!

These release notes cover the new features, as well as some backwards incompatible changes you’ll want to be aware of when upgrading from Django 1.7 or older versions. We’ve also begun the deprecation process for some features, and some features have reached the end of their deprecation process and have been removed.

Django 1.8 has been designated as Django’s second “Long-Term Support” (LTS) release. It will receive security updates for at least three years after its release. Support for the previous LTS, Django 1.4, will end 6 months from the release date of Django 1.8.

Due to the end of upstream support for Python 3.2 in February 2016, we won’t test Django 1.8.x on Python 3.2 after the end of 2016.

Django 1.8 is the first release to support Python 3.5.

Django 1.8 requires Python 2.7, 3.2, 3.3, 3.4, or 3.5. We highly recommend and only officially support the latest release of each series.

TestCase has been refactored to allow for data initialization at the class level using transactions and savepoints. Database backends which do not support transactions, like MySQL with the MyISAM storage engine, will still be able to run these tests but won’t benefit from the improvements. Tests are now run within two nested atomic() blocks: one for the whole class and one for each test.

A collection of database functions is also included with functionality such as Coalesce , Concat , and Substr .

Conditional Expressions allow you to use if … elif … else logic within queries.

Query Expressions allow you to create, customize, and compose complex SQL expressions. This has enabled annotate to accept expressions other than aggregates. Aggregates are now able to reference multiple fields, as well as perform arithmetic, similar to F() objects. order_by() has also gained the ability to accept expressions.

Django now has a module with extensions for PostgreSQL specific features, such as ArrayField , HStoreField , Range Fields , and unaccent lookup. A full breakdown of the features is available in the documentation .

Several features of the django-secure third-party library have been integrated into Django. django.middleware.security.SecurityMiddleware provides several security enhancements to the request/response cycle. The new --deploy option of the check command allows you to check your production settings file for ways to increase the security of your site.

Django 1.8 defines a stable API for integrating template backends. It includes built-in support for the Django template language and for Jinja2 . It supports rendering templates with multiple engines within the same project. Learn more about the new features in the topic guide and check the upgrade instructions for details.

The Model._meta object has been part of Django since the days of pre-0.96 “Magic Removal” – it just wasn’t an official, stable API. In recognition of this, we’ve endeavored to maintain backwards-compatibility with the old API endpoint where possible. However, API endpoints that aren’t part of the new official API have been deprecated and will eventually be removed. A guide to migrating from the old API to the new API has been provided.

Django now has a formalized API for Model._meta , providing an officially supported way to retrieve fields and filter fields based on their attributes .

An app without migrations with a ForeignKey to an app with migrations may now result in a foreign key constraint error when migrating the database or running tests. In Django 1.7, this could fail silently and result in a missing constraint. To resolve the error, add migrations to the app without them.

migrate now accepts the --fake-initial option to allow faking initial migrations. In 1.7 initial migrations were always automatically faked if all tables created in an initial migration already existed.

Be careful if you upgrade to Django 1.8 and skip Django 1.7. If you run manage.py migrate --fake , this migration will be skipped and you’ll see a RuntimeError: Error creating new content types. exception because the name column won’t be dropped from the database. Use manage.py migrate --fake-initial to fake only the initial migration instead.

The name field of django.contrib.contenttypes.models.ContentType has been removed by a migration and replaced by a property. That means it’s not possible to query or filter a ContentType by this field any longer.

When a translation doesn’t exist for a specific literal, the fallback is now taken from the LANGUAGE_CODE language (instead of from the untranslated msgid message).

django.utils.translation.get_language() now returns None instead of LANGUAGE_CODE when translations are temporarily deactivated.

When the leave_locale_alone attribute is False , translations are now deactivated instead of forcing the “en-us” locale. In the case your models contained non-English strings and you counted on English translations to be activated in management commands, this will not happen any longer. It might be that new database migrations are generated (once) after migrating to 1.8.

GenericIPAddressField.empty_strings_allowed is now False . Database backends that interpret empty strings as null (only Oracle among the backends that Django includes) will no longer convert null values back to an empty string. This is consistent with other backends.

Translatable strings set as the default parameter of the field are cast to concrete strings later, so the return type of Field.get_default() is different in some cases. There is no change to default values which are the result of a callable.

When following redirects, the test client now raises RedirectCycleError if it detects a loop or hits a maximum redirect limit (rather than passing silently).

Class-based views that use ModelFormMixin will raise an ImproperlyConfigured exception when both the fields and form_class attributes are specified. Previously, fields was silently ignored.

HttpRequest now has a simplified repr (e.g. <WSGIRequest: GET '/somepath/'> ). This won’t change the behavior of the SafeExceptionReporterFilter class.

Warnings from the MySQL database backend are no longer converted to exceptions when DEBUG is True .

Private APIs override_template_loaders and override_with_test_loader in django.test.utils were removed. Override TEMPLATES with override_settings instead.

The Memcached cache backends MemcachedCache and PyLibMCCache will delete a key if set() fails. This is necessary to ensure the cache_db session store always fetches the most current session data.

When iterating over lines, File now uses universal newlines . The following are recognized as ending a line: the Unix end-of-line convention '

' , the Windows convention '\r

' , and the old Macintosh convention '\r' .

By default, call_command now always skips the check framework (unless you pass it skip_checks=False ).

The CacheClass shim has been removed from all cache backends. These aliases were provided for backwards compatibility with Django 1.3. If you are still using them, please update your project to use the real class name found in the BACKEND key of the CACHES setting.

reverse() and reverse_lazy() now return Unicode strings instead of byte strings.

The default max size of the Oracle test tablespace has increased from 300M (or 200M, before 1.7.2) to 500M.

Seconds have been removed from any locales that had them in TIME_FORMAT , DATETIME_FORMAT , or SHORT_DATETIME_FORMAT .

For consistency with other major vendors, the en_GB locale now has Monday as the first day of the week.

Internal changes were made to the ClearableFileInput widget to allow more customization. The undocumented url_markup_template attribute was removed in favor of template_with_initial .

The block usertools in the base.html template of django.contrib.admin now requires the has_permission context variable to be set. If you have any custom admin views that use this template, update them to pass AdminSite.has_permission() as this new variable’s value or simply include AdminSite.each_context(request) in the context.

UserCreationForm.error_messages['duplicate_username'] is no longer used. If you wish to customize that error message, override it on the form using the 'unique' key in Meta.error_messages['username'] or, if you have a custom form field for 'username' , using the the 'unique' key in its error_messages argument.

ForeignKey.default_error_message['invalid'] has been changed from '%(model)s instance with pk %(pk)r does not exist.' to '%(model)s instance with %(field)s %(value)r does not exist.' If you are using this message in your own code, please update the list of interpolated parameters. Internally, Django will continue to provide the pk parameter in params for backwards compatibility.

The length template filter now returns 0 for an undefined variable, rather than an empty string.

GZipMiddleware used to disable compression for some content types when the request is from Internet Explorer, in order to work around a bug in IE6 and earlier. This behavior could affect performance on IE7 and later. It was removed.

Database connections are considered equal only if they’re the same object. They aren’t hashable any more.

You can revert to the old behavior by specifying autoescape=False if you are passing trusted content. This change doesn’t have any effect when using the corresponding filters in templates.

In order to make built-in template filters that output HTML “safe by default” when calling them in Python code, the following functions in django.template.defaultfilters have been changed to automatically escape their input value:

The data_types , data_types_suffix , and data_type_check_constraints attributes have moved from the DatabaseCreation class to DatabaseWrapper .

BaseDatabaseXXX classes have been moved to django.db.backends.base . Please import them from the new locations:

The following changes to the database backend API are documented to assist those writing third-party backends in updating their code:

Also note that get_all_related_objects() is deprecated in 1.8. See the upgrade guide for the new API.

To access the source model, you can use a pattern like this to write code that will work with both Django 1.8 and older versions:

and compare it to the behavior on older versions:

Consider this example from the tutorial in Django 1.8:

In earlier versions of Django, on a model with a reverse foreign key relationship (for example), model._meta.get_all_related_objects() returned the relationship as a django.db.models.related.RelatedObject with the model attribute set to the source of the relationship. Now, this method returns the relationship as django.db.models.fields.related.ManyToOneRel (private API RelatedObject has been removed), and the model attribute is set to the target of the relationship instead of the source. The source model is accessible on the related_model attribute instead.

If you’ve been relying on private APIs exposed in the django.template module, you may have to import them from django.template.base instead.

Django previously closed database connections between each test within a TestCase . This is no longer the case as Django now wraps the whole TestCase within a transaction. If some of your tests relied on the old behavior, you should have them inherit from TransactionTestCase instead.

The decorators override_settings() and modify_settings() now act at the class level when used as class decorators. As a consequence, when overriding setUpClass() or tearDownClass() , the super implementation should always be called.

The TemplateResponse constructor is designed to be a drop-in replacement for the render() function. However, it had a slight incompatibility, in that for TemplateResponse , context data from the passed in context dictionary could be shadowed by context data returned from context processors, whereas for render it was the other way around. This was a bug, and the behavior of render is more appropriate, since it allows the globally defined context processors to be overridden locally in the view. If you were relying on the fact context data in a TemplateResponse could be overridden using a context processor, you will need to change your code.

If you are using a custom user model that inherits from AbstractUser , you’ll need to run makemigrations and generate a migration for your app that contains that model. Also, if wish to set last_login to NULL for users who haven’t logged in, you can run this query:

The AbstractUser.last_login field now allows null values. Previously, it defaulted to the time when the user was created which was misleading if the user never logged in. If you are using the default user ( django.contrib.auth.models.User ), run the database migration included in contrib.auth .

Earlier versions of Django granted the CONNECT and RESOURCE roles to the test user on Oracle. These roles have been deprecated, so Django 1.8 uses the specific underlying privileges instead. This changes the privileges required of the main user for running tests (unless the project is configured to avoid creating a test user). The exact privileges required now are detailed in Oracle notes .

The end of upstream support periods was reached in July 2010 for Oracle 9.2, January 2012 for Oracle 10.1, and July 2013 for Oracle 10.2. As a consequence, Django 1.8 sets 11.1 as the minimum Oracle version it officially supports.

The end of upstream support periods was reached in January 2012 for MySQL 5.0 and December 2013 for MySQL 5.1. As a consequence, Django 1.8 sets 5.5 as the minimum MySQL version it officially supports.

Django also now requires the use of Psycopg2 version 2.4.5 or higher (or 2.5+ if you want to use django.contrib.postgres ).

This also includes dropping support for PostGIS 1.3 and 1.4 as these versions are not supported on versions of PostgreSQL later than 8.4.

The end of upstream support periods was reached in July 2014 for PostgreSQL 8.4. As a consequence, Django 1.8 sets 9.0 as the minimum PostgreSQL version it officially supports.

The old default 75 character max_length was not capable of storing all possible RFC3696/5321-compliant email addresses. In order to store all possible valid email addresses, the max_length has been increased to 254 characters. You will need to generate and apply database migrations for your affected models (or add max_length=75 if you wish to keep the length on your current fields). A migration for django.contrib.auth.models.User.email is included.

The validation also makes sure that the given field is relational:

select_related() now validates that the given fields actually exist. Previously, nonexistent fields were silently ignored. Now, an error is raised:

Querying for model lookups now checks if the object passed is of correct type and raises a ValueError if not. Previously, Django didn’t care if the object was of correct type; it just used the object’s related field attribute (e.g. id ) for the lookup. Now, an error is raised to prevent incorrect lookups:

The check also applies to the columns generated in an implicit ManyToManyField.through model. If you run into an issue there, use through to create an explicit model and then specify db_column on its column(s) as needed.

If you have an existing model where this check seems to be a false positive, for example on PostgreSQL where the name was already being truncated, simply use db_column to specify the name that’s being used.

A model check has been introduced to better alert users to this scenario before the actual creation of database tables.

A field name that’s longer than the column name length supported by a database can create problems. For example, with MySQL you’ll get an exception trying to create the column, and with PostgreSQL the column name is truncated by the database (you may see a warning in the PostgreSQL logs).

The method to add custom arguments to the test management command through the test runner has changed. Previously, you could provide an option_list class variable on the test runner to add more arguments (à la optparse ). Now to implement the same behavior, you have to create an add_arguments(cls, parser) class method on the test runner and call parser.add_argument to add any custom arguments, as parser is now an argparse.ArgumentParser instance.

If you have written a custom management command that only accepts positional arguments and you didn’t specify the args command variable, you might get an error like Error: unrecognized arguments: ... , as variable parsing is now based on argparse which doesn’t implicitly accept positional arguments. You can make your command backwards compatible by simply setting the args class variable. However, if you don’t have to keep compatibility with older Django versions, it’s better to implement the new add_arguments() method as described in Writing custom django-admin commands .

If you require allowing the assignment of unsaved instances (the old behavior) and aren’t concerned about the data loss possibility (e.g. you never save the objects to the database), you can disable this check by using the ForeignKey.allow_unsaved_instance_assignment attribute. (This attribute was removed in 1.8.4 as it’s no longer relevant.)

Now, an error will be raised to prevent data loss:

Previously, the assignment of an unsaved object would be silently ignored. For example:

A similar check on assignment to reverse one-to-one relations was removed in Django 1.8.5.

To more easily allow in-memory usage of models, this change was reverted in Django 1.8.4 and replaced with a check during model.save() . For example:

This has one backwards incompatible side effect, signal handlers triggered from these methods are now executed within the method’s transaction and any exception in a signal handler will prevent the whole operation.

Some operations on related objects such as add() or direct assignment ran multiple data modifying queries without wrapping them in transactions. To reduce the risk of data corruption, all data modifying methods that affect multiple related objects (i.e. add() , remove() , clear() , and direct assignment ) now perform their data modifying queries from within a transaction, provided your database supports transactions.

In addition to the changes outlined in this section, be sure to review the deprecation plan for any features that have been removed. If you haven’t updated your code within the deprecation timeline for a given feature, its removal may appear as a backwards incompatible change.

Features deprecated in 1.8¶

Selected methods in django.db.models.options.Options ¶ As part of the formalization of the Model._meta API (from the django.db.models.options.Options class), a number of methods have been deprecated and will be removed in Django 1.10: get_all_field_names()

get_all_related_objects()

get_all_related_objects_with_model()

get_all_related_many_to_many_objects()

get_all_related_m2m_objects_with_model()

get_concrete_fields_with_model()

get_field_by_name()

get_fields_with_model()

get_m2m_with_model() A migration guide has been provided to assist in converting your code from the old API to the new, official API.

django.conf.urls.patterns() ¶ In the olden days of Django, it was encouraged to reference views as strings in urlpatterns : urlpatterns = patterns ( '' , url ( '^$' , 'myapp.views.myview' ), ) and Django would magically import myapp.views.myview internally and turn the string into a real function reference. In order to reduce repetition when referencing many views from the same module, the patterns() function takes a required initial prefix argument which is prepended to all views-as-strings in that set of urlpatterns : urlpatterns = patterns ( 'myapp.views' , url ( '^$' , 'myview' ), url ( '^other/$' , 'otherview' ), ) In the modern era, we have updated the tutorial to instead recommend importing your views module and referencing your view functions (or classes) directly. This has a number of advantages, all deriving from the fact that we are using normal Python in place of “Django String Magic”: the errors when you mistype a view name are less obscure, IDEs can help with autocompletion of view names, etc. So these days, the above use of the prefix arg is much more likely to be written (and is better written) as: from myapp import views urlpatterns = patterns ( '' , url ( '^$' , views . myview ), url ( '^other/$' , views . otherview ), ) Thus patterns() serves little purpose and is a burden when teaching new users (answering the newbie’s question “why do I need this empty string as the first argument to patterns() ?”). For these reasons, we are deprecating it. Updating your code is as simple as ensuring that urlpatterns is a list of django.conf.urls.url() instances. For example: from django.conf.urls import url from myapp import views urlpatterns = [ url ( '^$' , views . myview ), url ( '^other/$' , views . otherview ), ]

Passing a string as view to url() ¶ Related to the previous item, referencing views as strings in the url() function is deprecated. Pass the callable view as described in the previous section instead.

Template-related settings¶ As a consequence of the multiple template engines refactor, several settings are deprecated in favor of TEMPLATES : ALLOWED_INCLUDE_ROOTS

TEMPLATE_CONTEXT_PROCESSORS

TEMPLATE_DEBUG

TEMPLATE_DIRS

TEMPLATE_LOADERS

TEMPLATE_STRING_IF_INVALID

django.core.context_processors ¶ Built-in template context processors have been moved to django.template.context_processors .

django.test.SimpleTestCase.urls ¶ The attribute SimpleTestCase.urls for specifying URLconf configuration in tests has been deprecated and will be removed in Django 1.10. Use @override_settings(ROOT_URLCONF=...) instead.

prefix argument to i18n_patterns() ¶ Related to the previous item, the prefix argument to django.conf.urls.i18n.i18n_patterns() has been deprecated. Simply pass a list of django.conf.urls.url() instances instead.

Using an incorrect count of unpacked values in the for template tag¶ Using an incorrect count of unpacked values in for tag will raise an exception rather than fail silently in Django 1.10.

Passing a dotted path to reverse() and url ¶ Reversing URLs by Python path is an expensive operation as it causes the path being reversed to be imported. This behavior has also resulted in a security issue. Use named URL patterns for reversing instead. If you are using django.contrib.sitemaps , add the name argument to the url that references django.contrib.sitemaps.views.sitemap() : from django.contrib.sitemaps.views import sitemap url ( r '^sitemap\.xml$' , sitemap , { 'sitemaps' : sitemaps }, name = 'django.contrib.sitemaps.views.sitemap' ) to ensure compatibility when reversing by Python path is removed in Django 1.10. Similarly for GIS sitemaps, add name='django.contrib.gis.sitemaps.views.kml' or name='django.contrib.gis.sitemaps.views.kmz' . If you are using a Python path for the LOGIN_URL or LOGIN_REDIRECT_URL setting, use the name of the url() instead.

Aggregate methods and modules¶ 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. If you were using the old modules, see Query Expressions for instructions on rewriting custom aggregates using the new stable API. The following methods and properties of django.db.models.sql.query.Query have also been deprecated and the backwards compatibility shims will be removed in Django 1.10: Query.aggregates , replaced by annotations .

, replaced by . Query.aggregate_select , replaced by annotation_select .

, replaced by . Query.add_aggregate() , replaced by add_annotation() .

, replaced by . Query.set_aggregate_mask() , replaced by set_annotation_mask() .

, replaced by . Query.append_aggregate_mask() , replaced by append_annotation_mask() .

Extending management command arguments through Command.option_list ¶ Management commands now use argparse instead of optparse to parse command-line arguments passed to commands. This also means that the way to add custom arguments to commands has changed: instead of extending the option_list class list, you should now override the add_arguments() method and add arguments through argparse.add_argument() . See this example for more details.

django.core.management.NoArgsCommand ¶ The class NoArgsCommand is now deprecated and will be removed in Django 1.10. Use BaseCommand instead, which takes no arguments by default.

Listing all migrations in a project¶ The --list option of the migrate management command is deprecated and will be removed in Django 1.10. Use showmigrations instead.

cache_choices option of ModelChoiceField and ModelMultipleChoiceField ¶ ModelChoiceField and ModelMultipleChoiceField took an undocumented, untested option cache_choices . This cached querysets between multiple renderings of the same Form object. This option is subject to an accelerated deprecation and will be removed in Django 1.9.

django.template.resolve_variable() ¶ The function has been informally marked as “Deprecated” for some time. Replace resolve_variable(path, context) with django.template.Variable(path).resolve(context) .

django.contrib.webdesign ¶ It provided the lorem template tag which is now included in the built-in tags. Simply remove 'django.contrib.webdesign' from INSTALLED_APPS and {% load webdesign %} from your templates.

error_message argument to django.forms.RegexField ¶ It provided backwards compatibility for pre-1.0 code, but its functionality is redundant. Use Field.error_messages['invalid'] instead.

Old unordered_list syntax¶ An older (pre-1.0), more restrictive and verbose input format for the unordered_list template filter has been deprecated: [ 'States' , [[ 'Kansas' , [[ 'Lawrence' , []], [ 'Topeka' , []]]], [ 'Illinois' , []]]] Using the new syntax, this becomes: [ 'States' , [ 'Kansas' , [ 'Lawrence' , 'Topeka' ], 'Illinois' ]]

django.forms.Field._has_changed() ¶ Rename this method to has_changed() by removing the leading underscore. The old name will still work until Django 1.10.

is_admin_site argument to django.contrib.auth.views.password_reset() ¶ It’s a legacy option that should no longer be necessary.

SubfieldBase ¶ django.db.models.fields.subclassing.SubfieldBase has been deprecated and will be removed in Django 1.10. Historically, it was used to handle fields where type conversion was needed when loading from the database, but it was not used in .values() calls or in aggregates. It has been replaced with from_db_value() . The new approach doesn’t call the to_python() method on assignment as was the case with SubfieldBase . If you need that behavior, reimplement the Creator class from Django’s source code in your project.

django.utils.checksums ¶ The django.utils.checksums module has been deprecated and will be removed in Django 1.10. The functionality it provided (validating checksum using the Luhn algorithm) was undocumented and not used in Django. The module has been moved to the django-localflavor package (version 1.1+).

InlineAdminForm.original_content_type_id ¶ The original_content_type_id attribute on InlineAdminForm has been deprecated and will be removed in Django 1.10. Historically, it was used to construct the “view on site” URL. This URL is now accessible using the absolute_url attribute of the form.

django.views.generic.edit.FormMixin.get_form() ’s form_class argument¶ FormMixin subclasses that override the get_form() method should make sure to provide a default value for the form_class argument since it’s now optional.

Rendering templates loaded by get_template() with a Context ¶ 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. Both classes provide a render() method, however, the former takes a django.template.Context as an argument while the latter expects a dict . This change is enforced through a deprecation path for Django templates. Since it’s easier to understand with examples, the upgrade guide shows how to adapt affected code. All this also applies to select_template() .

Template and Context classes in template responses¶ Some methods of SimpleTemplateResponse and TemplateResponse accepted django.template.Context and django.template.Template objects as arguments. They should now receive dict and backend-dependent template objects respectively. This also applies to the return types if you have subclassed either template response class. Check the template response API documentation for details.

current_app argument of template-related APIs¶ The following functions and classes will no longer accept a current_app parameter to set an URL namespace in Django 1.10: django.shortcuts.render()

django.template.Context()

django.template.RequestContext()

django.template.response.TemplateResponse() Set request.current_app instead, where request is the first argument to these functions or classes. If you’re using a plain Context , use a RequestContext instead.

dictionary and context_instance arguments of rendering functions¶ The following functions will no longer accept the dictionary and context_instance parameters in Django 1.10: django.shortcuts.render()

django.shortcuts.render_to_response()

django.template.loader.render_to_string() Use the context parameter instead. When dictionary is passed as a positional argument, which is the most common idiom, no changes are needed. If you’re passing a Context in context_instance , pass a dict in the context parameter instead. If you’re passing a RequestContext , pass the request separately in the request parameter. If you’re using context_instance=RequestContext(request)) with render_to_response() , use django.shortcuts.render() , which always makes RequestContext available, instead. For example: from django.shortcuts import render_to_response from django.template import RequestContext render_to_response ( 'template.html' , { ... }, context_instance = RequestContext ( request )) becomes: from django.shortcuts import render render ( request , 'template.html' , { ... })

dirs argument of template-finding functions¶ The following functions will no longer accept a dirs parameter to override TEMPLATE_DIRS in Django 1.10: django.template.loader.get_template()

django.template.loader.select_template()

django.shortcuts.render()

django.shortcuts.render_to_response() The parameter didn’t work consistently across different template loaders and didn’t work for included templates.

django.template.loader.BaseLoader ¶ django.template.loader.BaseLoader was renamed to django.template.loaders.base.Loader . If you’ve written a custom template loader that inherits BaseLoader , you must inherit Loader instead.

django.test.utils.TestTemplateLoader ¶ Private API django.test.utils.TestTemplateLoader is deprecated in favor of django.template.loaders.locmem.Loader and will be removed in Django 1.9.

Support for the max_length argument on custom Storage classes¶ Storage subclasses should add max_length=None as a parameter to get_available_name() and/or save() if they override either method. Support for storages that do not accept this argument will be removed in Django 1.10.

qn replaced by compiler ¶ In previous Django versions, various internal ORM methods (mostly as_sql methods) accepted a qn (for “quote name”) argument, which was a reference to a function that quoted identifiers for sending to the database. In Django 1.8, that argument has been renamed to compiler and is now a full SQLCompiler instance. For backwards-compatibility, calling a SQLCompiler instance performs the same name-quoting that the qn function used to. However, this backwards-compatibility shim is immediately deprecated: you should rename your qn arguments to compiler , and call compiler.quote_name_unless_alias(...) where you previously called qn(...) .

Default value of RedirectView.permanent ¶ The default value of the RedirectView.permanent attribute will change from True to False in Django 1.9.

Using AuthenticationMiddleware without SessionAuthenticationMiddleware ¶ django.contrib.auth.middleware.SessionAuthenticationMiddleware was added in Django 1.7. In Django 1.7.2, its functionality was moved to auth.get_user() and, for backwards compatibility, enabled only if 'django.contrib.auth.middleware.SessionAuthenticationMiddleware' appears in MIDDLEWARE_CLASSES . In Django 1.10, session verification will be enabled regardless of whether or not SessionAuthenticationMiddleware is enabled (at which point SessionAuthenticationMiddleware will have no significance). You can add it to your MIDDLEWARE_CLASSES sometime before then to opt-in. Please read the upgrade considerations first.

django.contrib.sitemaps.FlatPageSitemap ¶ django.contrib.sitemaps.FlatPageSitemap has moved to django.contrib.flatpages.sitemaps.FlatPageSitemap . The old import location is deprecated and will be removed in Django 1.9.

Model Field.related ¶ Private attribute django.db.models.Field.related is deprecated in favor of Field.rel . The latter is an instance of django.db.models.fields.related.ForeignObjectRel which replaces django.db.models.related.RelatedObject . The django.db.models.related module has been removed and the Field.related attribute will be removed in Django 1.10.

ssi template tag¶ The ssi template tag allows files to be included in a template by absolute path. This is of limited use in most deployment situations, and the include tag often makes more sense. This tag is now deprecated and will be removed in Django 1.10.

= as comparison operator in if template tag¶ Using a single equals sign with the {% if %} template tag for equality testing was undocumented and untested. It’s now deprecated in favor of == .

%(<foo>)s syntax in ModelFormMixin.success_url ¶ The legacy %(<foo>)s syntax in ModelFormMixin.success_url is deprecated and will be removed in Django 1.10.

GeoQuerySet aggregate methods¶ The collect() , extent() , extent3d() , make_line() , and unionagg() aggregate methods are deprecated and should be replaced by their function-based aggregate equivalents ( Collect , Extent , Extent3D , MakeLine , and Union ).