2012-10-30 21:02:54 +08:00
|
|
|
============================================
|
|
|
|
|
Django 1.6 release notes - UNDER DEVELOPMENT
|
|
|
|
|
============================================
|
|
|
|
|
|
|
|
|
|
Welcome to Django 1.6!
|
|
|
|
|
|
|
|
|
|
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.5 or older versions. We've also dropped some features, which are detailed in
|
|
|
|
|
:doc:`our deprecation plan </internals/deprecation>`, and we've `begun the
|
|
|
|
|
deprecation process for some features`_.
|
|
|
|
|
|
|
|
|
|
.. _`new features`: `What's new in Django 1.6`_
|
|
|
|
|
.. _`backwards incompatible changes`: `Backwards incompatible changes in 1.6`_
|
|
|
|
|
.. _`begun the deprecation process for some features`: `Features deprecated in 1.6`_
|
|
|
|
|
|
|
|
|
|
What's new in Django 1.6
|
|
|
|
|
========================
|
|
|
|
|
|
2012-11-18 03:24:54 +08:00
|
|
|
Minor features
|
|
|
|
|
~~~~~~~~~~~~~~
|
|
|
|
|
|
|
|
|
|
* Authentication backends can raise ``PermissionDenied`` to immediately fail
|
|
|
|
|
the authentication chain.
|
|
|
|
|
|
2012-12-13 19:33:11 +08:00
|
|
|
* The ``assertQuerysetEqual()`` now checks for undefined order and raises
|
|
|
|
|
``ValueError`` if undefined order is spotted. The order is seen as
|
|
|
|
|
undefined if the given ``QuerySet`` isn't ordered and there are more than
|
|
|
|
|
one ordered values to compare against.
|
|
|
|
|
|
2013-01-12 16:37:19 +08:00
|
|
|
* Added :meth:`~django.db.models.query.QuerySet.earliest` for symmetry with
|
|
|
|
|
:meth:`~django.db.models.query.QuerySet.latest`.
|
|
|
|
|
|
2012-10-30 21:02:54 +08:00
|
|
|
Backwards incompatible changes in 1.6
|
|
|
|
|
=====================================
|
|
|
|
|
|
2012-10-24 05:04:37 +08:00
|
|
|
* The ``django.db.models.query.EmptyQuerySet`` can't be instantiated any more -
|
|
|
|
|
it is only usable as a marker class for checking if
|
|
|
|
|
:meth:`~django.db.models.query.QuerySet.none` has been called:
|
|
|
|
|
``isinstance(qs.none(), EmptyQuerySet)``
|
|
|
|
|
|
2012-10-30 21:02:54 +08:00
|
|
|
.. warning::
|
|
|
|
|
|
|
|
|
|
In addition to the changes outlined in this section, be sure to review the
|
|
|
|
|
:doc:`deprecation plan </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.
|
|
|
|
|
|
|
|
|
|
Features deprecated in 1.6
|
|
|
|
|
==========================
|
2013-01-02 05:28:48 +08:00
|
|
|
|
|
|
|
|
``SEND_BROKEN_LINK_EMAILS`` setting
|
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
|
|
|
|
|
|
:class:`~django.middleware.common.CommonMiddleware` used to provide basic
|
|
|
|
|
reporting of broken links by email when ``SEND_BROKEN_LINK_EMAILS`` is set to
|
|
|
|
|
``True``.
|
|
|
|
|
|
|
|
|
|
Because of intractable ordering problems between
|
|
|
|
|
:class:`~django.middleware.common.CommonMiddleware` and
|
|
|
|
|
:class:`~django.middleware.locale.LocaleMiddleware`, this feature was split
|
|
|
|
|
out into a new middleware:
|
|
|
|
|
:class:`~django.middleware.common.BrokenLinkEmailsMiddleware`.
|
|
|
|
|
|
|
|
|
|
If you're relying on this feature, you should add
|
|
|
|
|
``'django.middleware.common.BrokenLinkEmailsMiddleware'`` to your
|
|
|
|
|
:setting:`MIDDLEWARE_CLASSES` setting and remove ``SEND_BROKEN_LINK_EMAILS``
|
|
|
|
|
from your settings.
|
