Thursday, August 29, 2024

Re: How to import UGETTEXT_LAZY ON DJANGO 4.0

please I change all my ugetext_lazy to gettext_lazy and am still getting the same error please how can you help me.

On Friday 10 December 2021 at 18:46:41 UTC+4 Jason wrote:

https://docs.djangoproject.com/en/4.0/releases/3.0/#id3
On Friday, December 10, 2021 at 12:01:03 AM UTC-5 ngal...@gmail.com wrote:

Thanks hopefully the same to ugettext

 

Kind Regards

 

Ngallen Ramadhan

T: +255 765 889 960 | Emial: ngal...@gmail.com | Skype: ngallen2

 

From: django...@googlegroups.com <django...@googlegroups.com> On Behalf Of David Nugent
Sent: 10 December 2021 07:50
To: django...@googlegroups.com
Subject: Re: How to import UGETTEXT_LAZY ON DJANGO 4.0

 

Simply change it to gettext_lazy. You don't need the deprecated functions, they were for python 2.

 

Regards, David

 

On Fri, Dec 10, 2021 at 3:43 PM <ngal...@gmail.com> wrote:

It seems Django has removed 'ugettext_lazy`(from django.utils.translation import ugettext_lazy as _) from Django version 4.0.x

How can I handle translation on Django version 4.0.x?

 

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/009b01d7ed80%246da44d40%2448ece7c0%24%40gmail.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/a7fc530c-31b3-4ece-931d-15979b1acdd2n%40googlegroups.com.

No comments:

Post a Comment