Fixed #22933 -- Deprecated django.template.resolve_variable().

2 files changed, 9 insertions, 0 deletions

diff --git a/docs/internals/deprecation.txt b/docs/internals/deprecation.txt
index 682cb6101a..cc219343a3 100644
--- a/docs/internals/deprecation.txt
+++ b/docs/internals/deprecation.txt
@@ -42,6 +42,8 @@ about each item can often be found in the release notes of two versions prior.
   :class:`~django.core.management.BaseCommand` instead, which takes no arguments
   by default.
 
+* ``django.template.resolve_variable`` will be removed.
+
 .. _deprecation-removed-in-1.9:
 
 1.9
diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt
index 1eafb3337e..381700557e 100644
--- a/docs/releases/1.8.txt
+++ b/docs/releases/1.8.txt
@@ -525,3 +525,10 @@ instead, which takes no arguments by default.
 option ``cache_choices``. This cached querysets between multiple renderings of
 the same ``Form`` object. This option is subject to an accelerated deprecation
 and will be removed in Django 1.9.
+
+``django.template.resolve_variable()``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The function has been informally marked as "Deprecated" for some time. Replace
+``resolve_variable(path, context)`` with
+``django.template.Variable(path).resolve(context)``.