#23441: Maximum recursion depth exceeded when using custom `inclusion_tag` with
recursion in templates and `django.template.loaders.cached.Loader`
---------------------------------+------------------------------------
     Reporter:  vstoykov         |                    Owner:  nobody
         Type:  Bug              |                   Status:  closed
    Component:  Template system  |                  Version:  1.7
     Severity:  Normal           |               Resolution:  fixed
     Keywords:                   |             Triage Stage:  Accepted
    Has patch:  1                |      Needs documentation:  0
  Needs tests:  1                |  Patch needs improvement:  0
Easy pickings:  0                |                    UI/UX:  0
---------------------------------+------------------------------------

Comment (by Tim Graham <timograham@…>):

 In [changeset:"5c63c45512eeca1f9c2dbdb0c46cbc7d9c550bdc" 5c63c45]:
 {{{
 #!CommitTicketReference repository=""
 revision="5c63c45512eeca1f9c2dbdb0c46cbc7d9c550bdc"
 [1.8.x] Fixed #23441, #24555 -- Improved the behavior of InclusionNode.

 This change:

 * Makes the InclusionNode cache-safe by removing render-time side effects
   to its nodelist.
 * Ensures the render_context stack is properly scoped and reset by
 updating
   the render call to use Template.render rather than Nodelist.render.

 Backport of 0808ccce3808235c5b5a56e3f689cec0d4bc0ebf from master
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/23441#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.251fa5772f37d331daaeb1d940386b23%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to