| 1 |
========================== |
| 2 |
Django 1.2.2 release notes |
| 3 |
========================== |
| 4 |
|
| 5 |
Welcome to Django 1.2.2! |
| 6 |
|
| 7 |
This is the second "bugfix" release in the Django 1.2 series, |
| 8 |
improving the stability and performance of the Django 1.2 codebase. |
| 9 |
|
| 10 |
Django 1.2.2 maintains backwards compatibility with Django |
| 11 |
1.2.1, but contain a number of fixes and other |
| 12 |
improvements. Django 1.2.2 is a recommended upgrade for any |
| 13 |
development or deployment currently using or targeting Django 1.2. |
| 14 |
|
| 15 |
For full details on the new features, backwards incompatibilities, and |
| 16 |
deprecated features in the 1.2 branch, see the :doc:`/releases/1.2`. |
| 17 |
|
| 18 |
One new feature |
| 19 |
=============== |
| 20 |
|
| 21 |
Ordinarily, a point release would not include new features, but in the |
| 22 |
case of Django 1.2.2, we have made an exception to this rule. |
| 23 |
|
| 24 |
In order to test a bug fix that forms part of the 1.2.2 release, it |
| 25 |
was necessary to add a feature -- the ``enforce_csrf_checks`` flag -- |
| 26 |
to the :ref:`test client <test-client>`. This flag forces |
| 27 |
the test client to perform full CSRF checks on forms. The default |
| 28 |
behavior of the test client hasn't changed, but if you want to do |
| 29 |
CSRF checks with the test client, it is now possible to do so. |