Fixed #28125 -- Clarified 1.11 release note about Template.render() prohibiting non-dict context.
This commit is contained in:
parent
8bf96c109f
commit
bce5cc57e9
|
@ -601,14 +601,15 @@ Some widget values, such as ``<select>`` options, are now localized if
|
||||||
widget templates that uses the :ttag:`localize` template tag to turn off
|
widget templates that uses the :ttag:`localize` template tag to turn off
|
||||||
localization.
|
localization.
|
||||||
|
|
||||||
``django.Template.render()`` prohibits non-dict context
|
``django.template.backends.django.Template.render()`` prohibits non-dict context
|
||||||
-------------------------------------------------------
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
For compatibility with multiple template engines, ``django.Template.render()``
|
For compatibility with multiple template engines,
|
||||||
must receive a dictionary of context rather than ``Context`` or
|
``django.template.backends.django.Template.render()`` (returned from high-level
|
||||||
``RequestContext``. If you were passing either of the two classes, pass a
|
template loader APIs such as ``loader.get_template()``) must receive a
|
||||||
dictionary instead -- doing so is backwards-compatible with older versions of
|
dictionary of context rather than ``Context`` or ``RequestContext``. If you
|
||||||
Django.
|
were passing either of the two classes, pass a dictionary instead -- doing so
|
||||||
|
is backwards-compatible with older versions of Django.
|
||||||
|
|
||||||
Model state changes in migration operations
|
Model state changes in migration operations
|
||||||
-------------------------------------------
|
-------------------------------------------
|
||||||
|
|
Loading…
Reference in New Issue