3
==========================
4
Django 1.0.1 release notes
5
==========================
7
Welcome to Django 1.0.1!
9
This is the first "bugfix" release in the Django 1.0 series, improving
10
the stability and performance of the Django 1.0 codebase. As such,
11
Django 1.0.1 contains no new features (and, pursuant to `our
12
compatibility policy`_, maintains backwards compatibility with Django
13
1.0), but does contain a number of fixes and other
14
improvements. Django 1.0.1 is a recommended upgrade for any
15
development or deployment currently using or targeting Django 1.0.
18
Fixes and improvements in Django 1.0.1
19
======================================
21
Django 1.0.1 contains over two hundred fixes to the original Django
22
1.0 codebase; full details of every fix are available in `the
23
Subversion log of the 1.0.X branch`_, but here are some of the
26
* Several fixes in ``django.contrib.comments``, pertaining to RSS
27
feeds of comments, default ordering of comments and the XHTML and
28
internationalization of the default templates for comments.
30
* Multiple fixes for Django's support of Oracle databases, including
31
pagination support for GIS QuerySets, more efficient slicing of
32
results and improved introspection of existing databases.
34
* Several fixes for query support in the Django object-relational
35
mapper, including repeated setting and resetting of ordering and
36
fixes for working with ``INSERT``-only queries.
38
* Multiple fixes for inline forms in formsets.
40
* Multiple fixes for ``unique`` and ``unique_together`` model
41
constraints in automatically-generated forms.
43
* Fixed support for custom callable ``upload_to`` declarations when
44
handling file uploads through automatically-generated forms.
46
* Fixed support for sorting an admin change list based on a callable
47
attributes in ``list_display``.
49
* A fix to the application of autoescaping for literal strings passed
50
to the ``join`` template filter. Previously, literal strings passed
51
to ``join`` were automatically escaped, contrary to `the documented
52
behavior for autoescaping and literal strings`_. Literal strings
53
passed to ``join`` are no longer automatically escaped, meaning you
54
must now manually escape them; this is an incompatibility if you
55
were relying on this bug, but not if you were relying on escaping
56
behaving as documented.
58
* Improved and expanded translation files for many of the languages
59
Django supports by default.
61
* And as always, a large number of improvements to Django's
62
documentation, including both corrections to existing documents and
63
expanded and new documentation.
65
.. _our compatibility policy: http://docs.djangoproject.com/en/dev/misc/api-stability/
66
.. _the Subversion log of the 1.0.X branch: http://code.djangoproject.com/log/django/branches/releases/1.0.X
67
.. _the documented behavior for autoescaping and literal strings: http://docs.djangoproject.com/en/dev/topics/templates/#string-literals-and-automatic-escaping