Closed ma-adrian closed 2 years ago
The problem was related to my project because of using jinja2.ext.with_ and jinja2.ext.autoescape which were deprecated. Sorry for the inconvenience.
So has this been fixed?
I am able to reproduce this issue with Django v4.1.3, Django-Jinja2 v2.10.2, and Jinja2 v3.1.2?
The implication is that on March 29th, this was a non-issue? But it's still happening 11/22/2022? Does a release need to be made? Does it need to be released to PyPi?
Hi, I just tried to update my jinja2 version from 3.0.3 to 3.1.0. I'm not entirely sure if this is a django or django-jinja problem but it seems like the new version is breaking stuff in backend.py