|
1 ========================== |
|
2 Django 1.2.4 release notes |
|
3 ========================== |
|
4 |
|
5 Welcome to Django 1.2.4! |
|
6 |
|
7 This is the fourth "bugfix" release in the Django 1.2 series, |
|
8 improving the stability and performance of the Django 1.2 codebase. |
|
9 |
|
10 Django 1.2.4 maintains backwards compatibility with Django |
|
11 1.2.3, but contain a number of fixes and other |
|
12 improvements. Django 1.2.4 is a recommended upgrade for any |
|
13 development or deployment currently using or targeting Django 1.2. |
|
14 |
|
15 For full details on the new features, backwards incompatibilities, and |
|
16 deprecated features in the 1.2 branch, see the :doc:`/releases/1.2`. |
|
17 |
|
18 One new feature |
|
19 =============== |
|
20 |
|
21 Ordinarily, a point release would not include new features, but in the |
|
22 case of Django 1.2.4, we have made an exception to this rule. |
|
23 |
|
24 One of the bugs fixed in Django 1.2.4 involves a set of |
|
25 circumstances whereby a running a test suite on a multiple database |
|
26 configuration could cause the original source database (i.e., the |
|
27 actual production database) to be dropped, causing catastrophic loss |
|
28 of data. In order to provide a fix for this problem, it was necessary |
|
29 to introduce a new setting -- :setting:`TEST_DEPENDENCIES` -- that |
|
30 allows you to define any creation order dependencies in your database |
|
31 configuration. |
|
32 |
|
33 Most users -- even users with multiple-database configurations -- need |
|
34 not be concerned about the data loss bug, or the manual configuration of |
|
35 :setting:`TEST_DEPENDENCIES`. See the `original problem report`_ |
|
36 documentation on :ref:`controlling the creation order of test |
|
37 databases <topics-testing-creation-dependencies>` for details. |
|
38 |
|
39 .. _original problem report: http://code.djangoproject.com/ticket/14415 |
|
40 |
|
41 GeoDjango |
|
42 ========= |
|
43 |
|
44 The function-based :setting:`TEST_RUNNER` previously used to execute |
|
45 the GeoDjango test suite, :func:`django.contrib.gis.tests.run_gis_tests`, |
|
46 was finally deprecated in favor of a class-based test runner, |
|
47 :class:`django.contrib.gis.tests.GeoDjangoTestSuiteRunner`, added in this |
|
48 release. |
|
49 |
|
50 In addition, the GeoDjango test suite is now included when |
|
51 :ref:`running the Django test suite <running-unit-tests>` with ``runtests.py`` |
|
52 and using :ref:`spatial database backends <spatial-backends>`. |