#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
-------------------------------+-----------------------------------------
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>
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/0107018af9219810-d5e99556-3302-41c8-8125-e4cfe19bfaa2-000000%40eu-central-1.amazonses.com.
