Closed ShaheedHaque closed 2 years ago
Like you said, this is really an issue with Jinja2's code.
Here's the commit from 2008 where they added the usage of ugettext
: https://github.com/pallets/jinja/commit/3213355aef195818c282dabe51dfd5694c26d5f6#diff-b172bf04c4b9718c7c40ed89af39e268091b058c5fa97c788202175bf3185ef2
Luckily, it looks like their code is written in a way where Jinja only uses ugettext
if the template engine provides it, but will otherwise happily use gettext
. So the error should just go away once you upgrade to Django 4.
As of recent versions,
django.utils.translation.ugettext()
is deprecated. This results in warnings like this fragment:I can see the code involved is in JInja2 itself, but was hoping there might be a way to deal with this here in the first instance?