p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Tweaked a bit the release notes document. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15801 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Ramiro Morales 2011-03-14 13:53:45 +00:00
parent e494f88be0
commit 12b5152233
1 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
docs/releases/1.3.txt
View File

@ -211,7 +211,7 @@ The GeoDjango test suite is now included when
when using :ref:`spatial database backends <spatial-backends>`. when using :ref:`spatial database backends <spatial-backends>`.
``MEDIA_URL`` and ``STATIC_URL`` must end in a slash ``MEDIA_URL`` and ``STATIC_URL`` must end in a slash
---------------------------------------------------- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Previously, the ``MEDIA_URL`` setting only required a trailing slash if it Previously, the ``MEDIA_URL`` setting only required a trailing slash if it
contained a suffix beyond the domain name. contained a suffix beyond the domain name.
@ -555,9 +555,9 @@ test case.
Changed priority of translation loading Changed priority of translation loading
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work has been done to homogeneize, simplify, rationalize and properly document Work has been done to simplify, rationalize and properly document the algorithm
the algorithm used by Django at runtime to build translations from the used by Django at runtime to build translations from the differents translations
differents translations found on disk, namely: found on disk, namely:
For translatable literals found in Python code and templates (``'django'`` For translatable literals found in Python code and templates (``'django'``
gettext domain): gettext domain):
@ -592,11 +592,11 @@ domain):
:ref:`javascript_catalog view <javascript_catalog-view>`. Paths listed first :ref:`javascript_catalog view <javascript_catalog-view>`. Paths listed first
have higher precedence than the ones listed later. have higher precedence than the ones listed later.
* Translations under the ``locale`` sbdirectory of the *project directory* have * Translations under the ``locale`` subdirectory of the *project directory*
never been taken in account for JavaScript translations and remain in the have never been taken in account for JavaScript translations and remain in
same situation considering the deprecation of such location. the same situation considering the deprecation of such location.
.. _corresponding deprecated features section: loading_of_translations_from_the_project_directory_ .. _corresponding deprecated features section: loading_of_project_level_translations_
Transaction management Transaction management
~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~
@ -812,16 +812,16 @@ which was a bug-fix wrapper around the standard library ``SimpleCookie``. As the
fixes are moving upstream, this is now deprecated - you should use ``from fixes are moving upstream, this is now deprecated - you should use ``from
django.http import SimpleCookie`` instead. django.http import SimpleCookie`` instead.
.. _loading_of_translations_from_the_project_directory: .. _loading_of_project_level_translations:
Loading of translations from the project directory Loading of *project-level* translations
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This release of Django starts the deprecation process for inclusion of This release of Django starts the deprecation process for inclusion of
translations located under the *project path* in the translation building translations located under the so-called *project path* in the translation
process performed at runtime. The :setting:`LOCALE_PATHS` setting can be used building process performed at runtime. The :setting:`LOCALE_PATHS` setting can
for the same task by including in it the filesystem path to the ``locale`` be used for the same task by adding the filesystem path to a ``locale``
directory containing project-level translations. directory containing project-level translations to the value of that setting.
Rationale for this decision: Rationale for this decision:
@ -835,17 +835,17 @@ Rationale for this decision:
scenario is more complex than the basic one. e.g. it fails when the settings scenario is more complex than the basic one. e.g. it fails when the settings
module is a directory (ticket #10765). module is a directory (ticket #10765).
* Potential for strange development- and deployment-time problems like the * There are potential strange development- and deployment-time problems like the
fact that the ``project_dir/locale/`` subdir can generate spurious error fact that the ``project_dir/locale/`` subdir can generate spurious error
messages when the project directory is included in the Python path (default messages when the project directory is added to the Python path (``manage.py
behavior of ``manage.py runserver``) and then it clashes with the equally runserver`` does this) and then it clashes with the equally named standard
named standard library module, this is a typical warming message:: library module, this is a typical warning message::
/usr/lib/python2.6/gettext.py:49: ImportWarning: Not importing directory '/path/to/project/dir/locale': missing __init__.py. /usr/lib/python2.6/gettext.py:49: ImportWarning: Not importing directory '/path/to/project/locale': missing __init__.py.
import locale, copy, os, re, struct, sys import locale, copy, os, re, struct, sys
* This location wasn't included in the translation building process for * This location wasn't included in the translation building process for
JavaScript literals. JavaScript literals. This deprecation removes such inconsistency.
``PermWrapper`` moved to ``django.contrib.auth.context_processors`` ``PermWrapper`` moved to ``django.contrib.auth.context_processors``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~