I guess this should go to django-users (usage questions). It's not clear to me how this is related to the development of Django itself. To increase the likelihood of getting an answer, make the code example more complete and find the commit in Django where the behavior changed. I can't answer the question in its current form.
On Thursday, February 18, 2016 at 1:16:19 PM UTC-5, John Bazik wrote: > > I'm looking at code that does this: > > context = context.new(context) > > Prior to 1.7, I assume that worked since a context was a dict. Now that > it's a stack, it breaks. > > I could suggest they use flatten: > > context = context.new(context.flatten()) > > but that's not exactly a copy, which is what I think they're after. > > What do you think they should be doing? > > John > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f47d724a-7edf-4506-93a9-b8751517897e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
