Debian Codegraph @

docs/releases/1.0.2.txt

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