#36796: URL resolution breaks if route defined with lazy string and uses an
include
------------------------------------+------------------------------------
Reporter: Andrea Angelini | Owner: (none)
Type: Bug | Status: new
Component: Core (URLs) | Version: 6.0
Severity: Release blocker | Resolution:
Keywords: gettext_lazy, lazy | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+------------------------------------
Comment (by Jake Howard):
I'd missed that lazy string were accepted, and surprised a test didn't
cover this behaviour.
Just handling the `elif` case won't quite work, since there's also the
endpoint case. Converting `self._route` to a string (as part of `match`,
rather than the constructor so it's evaluated in the correct context)
sounds like the right solution. It'd be nice if the conversion only
happens once per `match` to avoid unnecessary extra work.
--
Ticket URL: <https://code.djangoproject.com/ticket/36796#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 visit
https://groups.google.com/d/msgid/django-updates/0107019b1324d416-fc3cb5be-cf95-4a69-9c85-adcb98abcf6f-000000%40eu-central-1.amazonses.com.
