3
==========================
4
Django 1.1.2 release notes
5
==========================
7
Welcome to Django 1.1.2!
9
This is the second "bugfix" release in the Django 1.1 series,
10
improving the stability and performance of the Django 1.1 codebase.
12
Django 1.1.2 maintains backwards compatibility with Django
13
1.1.0, but contain a number of fixes and other
14
improvements. Django 1.1.2 is a recommended upgrade for any
15
development or deployment currently using or targeting Django 1.1.
17
For full details on the new features, backwards incompatibilities, and
18
deprecated features in the 1.1 branch, see the :ref:`releases-1.1`.
20
Backwards-incompatible changes in 1.1.2
21
=======================================
23
Test runner exit status code
24
----------------------------
26
The exit status code of the test runners (``tests/runtests.py`` and ``python
27
manage.py test``) no longer represents the number of failed tests, since a
28
failure of 256 or more tests resulted in a wrong exit status code. The exit
29
status code for the test runner is now 0 for success (no failing tests) and 1
30
for any number of test failures. If needed, the number of test failures can be
31
found at the end of the test runner's output.
36
To fix bugs with cookies in Internet Explorer, Safari, and possibly other
37
browsers, our encoding of cookie values was changed so that the characters
38
comma and semi-colon are treated as non-safe characters, and are therefore
39
encoded as ``\054`` and ``\073`` respectively. This could produce backwards
40
incompatibilities, especially if you are storing comma or semi-colon in
41
cookies and have javascript code that parses and manipulates cookie values
47
Ordinarily, a point release would not include new features, but in the
48
case of Django 1.1.2, we have made an exception to this rule. Django
49
1.2 (the next major release of Django) will contain a feature that
50
will improve protection against Cross-Site Request Forgery (CSRF)
51
attacks. This feature requires the use of a new :ttag:`csrf_token`
52
template tag in all forms that Django renders.
54
To make it easier to support both 1.1.X and 1.2.X versions of Django with
55
the same templates, we have decided to introduce the :ttag:`csrf_token` template
56
tag to the 1.1.X branch. In the 1.1.X branch, :ttag:`csrf_token` does nothing -
57
it has no effect on templates or form processing. However, it means that the
58
same template will work with Django 1.2.