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