A final *final* clarification in the release notes.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@13274 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
d88d0ec336
commit
c40b131ed5
|
@ -366,13 +366,14 @@ Backwards-incompatible changes in 1.2
|
||||||
|
|
||||||
Wherever possible the new features above have been introduced in a
|
Wherever possible the new features above have been introduced in a
|
||||||
backwards-compatible manner per :ref:`our API stability policy
|
backwards-compatible manner per :ref:`our API stability policy
|
||||||
<misc-api-stability>` policy. This means that existing code which
|
<misc-api-stability>` policy. This means that practically all existing
|
||||||
worked with Django 1.1 will continue to work with Django 1.2; such
|
code which worked with Django 1.1 will continue to work with Django
|
||||||
code will, however, begin issuing warnings (see below for details).
|
1.2; such code will, however, begin issuing warnings (see below for
|
||||||
|
details).
|
||||||
|
|
||||||
However, a handful of features *have* changed in ways that, for some
|
However, a handful of features *have* changed in ways that, for some
|
||||||
users, will be backwards-incompatible. Those changes are detailed
|
users, will be immediately backwards-incompatible. Those changes are
|
||||||
below.
|
detailed below.
|
||||||
|
|
||||||
CSRF Protection
|
CSRF Protection
|
||||||
---------------
|
---------------
|
||||||
|
|
Loading…
Reference in New Issue