#34886: Sample use of lazy in delayed translations is not valid in Django 4.1
and
4.2.
-------------------------------+-----------------------------------------
Reporter: Stefan Hammer | Owner: SanjayBisht96
Type: Bug | Status: assigned
Component: Documentation | Version: 4.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+-----------------------------------------
Changes (by Mariusz Felisiak):
* 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>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018af95f445e-20053ea0-168a-4961-a9e7-10d017606e94-000000%40eu-central-1.amazonses.com.
