  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 :ref:`dropped some features
  <deprecation-removed-in-1.9>` that have reached the end of their deprecation
  cycle, and we've `begun the deprecation process for some features`_.
  
  .. _`new features`: `What's new in Django 1.9`_
  .. _`backwards incompatible changes`: `Backwards incompatible changes in 1.9`_
  .. _`dropped some features`: `Features removed in 1.9`_
  .. _`begun the deprecation process for some features`: `Features deprecated in 1.9`_
 
</s> remove .. removed-features-1.9:
 </s> add .. _removed-features-1.9: </s> remove     :doc:`deprecation timeline </internals/deprecation>` 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.
 </s> add     :ref:`removed-features-1.9` for the features that have reached the end of
    their deprecation cycle and therefore 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. </s> remove 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 3.3, and added support for Python 3.5.
 </s> add Django 1.9 requires Python 2.7, 3.4, or 3.5. We **highly recommend** and only
officially support the latest release of each series.

Since Django 1.8, we've dropped support for Python 3.2 and 3.3, and added
support for Python 3.5. </s> remove If you fail to do so, Django 1.9 and 2.0 will perform the conversion like
earlier versions but emit a deprecation warning. Django 2.0 won't perform any
 </s> add If you fail to do so, the conversion will be performed as in earlier versions
(with a deprecation warning) up until Django 1.11. Django 2.0 won't perform any </s> remove   including ``django.contrib.auth`` in :setting:`INSTALLED_APPS` (this raised
  a deprecation warning in older versions and is no longer supported in
 </s> add   including ``django.contrib.auth`` in :setting:`INSTALLED_APPS` (doing so
  raised a deprecation warning in older versions and is no longer supported in
1.8 or older versions. We've :ref:`dropped some features<removed-features-1.9>`
that have reached the end of their deprecation cycle, and we've `begun the
deprecation process for some features`_.
  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 :ref:`dropped some features<removed-features-1.9>`
that have reached the end of their deprecation cycle, and we've `begun the
deprecation process for some features`_.
1.8 or older versions. We've :ref:`dropped some features<removed-features-1.9>`
that have reached the end of their deprecation cycle, and we've `begun the
deprecation process for some features`_.
1.8 or older versions. We've :ref:`dropped some features<removed-features-1.9>`
that have reached the end of their deprecation cycle, and we've `begun the
deprecation process for some features`_.
  
  .. _`new features`: `What's new in Django 1.9`_
  .. _`backwards incompatible changes`: `Backwards incompatible changes in 1.9`_
  .. _`dropped some features`: `Features removed in 1.9`_
  .. _`begun the deprecation process for some features`: `Features deprecated in 1.9`_
keep keep keep keep replace replace replace keep keep keep keep keep
 Alphabetized a few sections in the 1.9 release notes + made a few tweaks. 
docs/releases/1.9.txt