Welcome to Django 1.9!
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.8 or older versions. We’ve dropped some features that have reached the end of their deprecation cycle, and we’ve begun the deprecation process for some features.
Like Django 1.8, Django 1.9 requires Python 2.7 or above, though we highly recommend the latest minor release. We’ve dropped support for Python 3.2 and added support for Python 3.5.
...
Warning
In addition to the changes outlined in this section, be sure to review the deprecation timeline 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.
The default settings in django.conf.global_settings were a combination of lists and tuples. All settings that were formerly tuples are now lists.
Django template loaders previously required an is_usable attribute to be defined. If a loader was configured in the template settings and this attribute was False, the loader would be silently ignored. In practice, this was only used by the egg loader to detect if setuptools was installed. The is_usable attribute is now removed and the egg loader instead fails at runtime if setuptools is not installed.
Django 1.4 added the assignment_tag helper to ease the creation of template tags that store results in a template variable. The simple_tag() helper has gained this same ability, making the assignment_tag obsolete. Tags that use assignment_tag should be updated to use simple_tag.
These features have reached the end of their deprecation cycle and so have been removed in Django 1.9 (please see the deprecation timeline for more details):
Feb 10, 2015