PageRenderTime 20ms CodeModel.GetById 14ms RepoModel.GetById 0ms app.codeStats 0ms

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