* owner: nobody => SanjayBisht96
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/34886#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Comment (by Stefan Hammer):
Thanks for the information. I'm also happy that someone assigned itself to
this, because this would be my first contribution and that would take some
time...
But just to be sure: the sample would work in Django 5.0 due to the fix
you've mentioned, but this whole
[https://docs.djangoproject.com/en/dev/topics/i18n/translation/#other-
uses-of-lazy-in-delayed-translations docs] block could actually be removed
for Django >=4.1, because since then `mark_safe()` preserves lazy objects
and therefore a custom helper like that `mark_safe_lazy()` isn't required
anymore. Right?
--
Ticket URL: <https://code.djangoproject.com/ticket/34886#comment:3>
* cc: Claude Paroz (added)
Comment:
Replying to [comment:3 Stefan Hammer]:
> But just to be sure: the sample would work in Django 5.0 due to the fix
you've mentioned, but this whole
[https://docs.djangoproject.com/en/dev/topics/i18n/translation/#other-
uses-of-lazy-in-delayed-translations docs] block could actually be removed
for Django >=4.1, because since then `mark_safe()` preserves lazy objects
and therefore a custom helper like that `mark_safe_lazy()` isn't required
anymore. Right?
This example could stay but with a different function, or maybe it's not
worth keeping 🤷 Originally it was reported for `mark_safe()`. What do you
think, Claude?
--
Ticket URL: <https://code.djangoproject.com/ticket/34886#comment:4>
Comment (by Claude Paroz):
I think we might keep the section by using any string-related method of
the standard lib, like `isascii()` for example.
--
Ticket URL: <https://code.djangoproject.com/ticket/34886#comment:5>