diff options
| author | Aymeric Augustin <aymeric.augustin@m4x.org> | 2014-12-17 22:10:57 +0100 |
|---|---|---|
| committer | Aymeric Augustin <aymeric.augustin@m4x.org> | 2014-12-28 17:02:30 +0100 |
| commit | cf0fd65ed42d5d4f0585da413db4b1cf7c6b0d1a (patch) | |
| tree | 3f4f652525adf16178018e4ce0c7eddeb0f61360 /docs/releases/1.2.txt | |
| parent | d3a982556d655adcf4ba331d2def685d8249170f (diff) | |
Deprecated TEMPLATE_LOADERS.
Diffstat (limited to 'docs/releases/1.2.txt')
| -rw-r--r-- | docs/releases/1.2.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/releases/1.2.txt b/docs/releases/1.2.txt index 422dff10e5..6d06fa49b2 100644 --- a/docs/releases/1.2.txt +++ b/docs/releases/1.2.txt @@ -267,9 +267,9 @@ opposed to functions, the only method available until Django 1.1. All the template loaders :ref:`shipped with Django <template-loaders>` have been ported to the new API but they still implement the function-based API and the template core machinery still accepts function-based loaders (builtin or -third party) so there is no immediate need to modify your -:setting:`TEMPLATE_LOADERS` setting in existing projects, things will keep -working if you leave it untouched up to and including the Django 1.3 release. +third party) so there is no immediate need to modify your ``TEMPLATE_LOADERS`` +setting in existing projects, things will keep working if you leave it +untouched up to and including the Django 1.3 release. If you have developed your own custom template loaders we suggest to consider porting them to a class-based implementation because the code for backwards |