#35738: Deprecate double-dot variable lookups
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: Sanjeev
Type: | Holla S
Cleanup/optimization | Status: assigned
Component: Template system | Version: dev
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 Adam Johnson):
> When a double-dot variable lookup is used, a warning with
RemovedInDjango60Warning should be raised?
No, target 6.1 for removal, using `RemovedInDjango61Warning`.
See: https://docs.djangoproject.com/en/dev/internals/release-process
/#internal-release-deprecation-policy
> Also I noticed one more thing, that is, the warning message can be seen
in the console only once because Django caches templates after they are
compiled, so warnings are triggered only during the initial compilation.
So is there any work around for this or is this fine?
This is fine, and I think desirable. We don’t want to spam production logs
where a dot-dot has been deployed.
--
Ticket URL: <https://code.djangoproject.com/ticket/35738#comment:7>
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/01070191c802016f-6ec5e9b6-4480-4f17-90df-f1858aa41547-000000%40eu-central-1.amazonses.com.
