Closed StefanBrand closed 2 years ago
I'm also getting this. It seems that force_text
has been removed from Django 4.0, and replaced with force_str
.
This package also has the same problem:
There is also a similar issue with ugettext
.
To mitigate this you can add the following monkeypatch to your settings.py
:
import django
from django.utils.encoding import force_str
django.utils.encoding.force_text = force_str
from django.utils.translation import gettext
django.utils.translation.ugettext = gettext
I'm also seeing this error in one of my apps.
Django 4.0 Release Notes say:
django.utils.translation.ugettext()
, ugettext_lazy()
, ugettext_noop()
, ungettext()
, and ungettext_lazy()
are removed.django.utils.encoding.force_text()
and smart_text()
are removed.
Features removed in 4.0