/docs/releases/1.0.2.txt

https://code.google.com/p/mango-py/ · Plain Text · 51 lines · 39 code · 12 blank · 0 comment · 0 complexity · 611024a6a64014692d02058438b28fc9 MD5 · raw file

  1. ==========================
  2. Django 1.0.2 release notes
  3. ==========================
  4. Welcome to Django 1.0.2!
  5. This is the second "bugfix" release in the Django 1.0 series,
  6. improving the stability and performance of the Django 1.0 codebase. As
  7. such, Django 1.0.2 contains no new features (and, pursuant to
  8. :doc:`our compatibility policy </misc/api-stability>`, maintains backwards compatibility with Django
  9. 1.0.0), but does contain a number of fixes and other
  10. improvements. Django 1.0.2 is a recommended upgrade for any
  11. development or deployment currently using or targeting Django 1.0.
  12. Fixes and improvements in Django 1.0.2
  13. ======================================
  14. The primary reason behind this release is to remedy an issue in the
  15. recently-released Django 1.0.1; the packaging scripts used for Django
  16. 1.0.1 omitted some directories from the final release package,
  17. including one directory required by ``django.contrib.gis`` and part of
  18. Django's unit-test suite.
  19. Django 1.0.2 contains updated packaging scripts, and the release
  20. package contains the directories omitted from Django 1.0.1. As such,
  21. this release contains all of the fixes and improvements from Django
  22. 1.0.1; see :doc:`the Django 1.0.1 release notes </releases/1.0.1>` for
  23. details.
  24. Additionally, in the period since Django 1.0.1 was released:
  25. * Updated Hebrew and Danish translations have been added.
  26. * The default ``__repr__`` method of Django models has been made more
  27. robust in the face of bad Unicode data coming from the
  28. ``__unicode__`` method; rather than raise an exception in such
  29. cases, ``repr()`` will now contain the string "[Bad Unicode data]"
  30. in place of the invalid Unicode.
  31. * A bug involving the interaction of Django's ``SafeUnicode`` class
  32. and the MySQL adapter has been resolved; ``SafeUnicode`` instances
  33. (generated, for example, by template rendering) can now be assigned
  34. to model attributes and saved to MySQL without requiring an explicit
  35. intermediate cast to ``unicode``.
  36. * A bug affecting filtering on a nullable ``DateField`` in SQLite has
  37. been resolved.
  38. * Several updates and improvements have been made to Django's
  39. documentation.