Opened 10 years ago
Last modified 17 months ago
#25466 closed Bug
django.template.loader.LoaderOrigin was removed without proper deprecation — at Version 3
| Reported by: | Joey Wilhelm | Owned by: | nobody |
|---|---|---|---|
| Component: | Template system | Version: | 1.9a1 |
| Severity: | Release blocker | Keywords: | |
| Cc: | Florian Apolloner | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
#15053 caused the removal of django.template.loader.LoadOrigin (and django.template.StringOrigin), in favor of django.template.base.Origin, for Django 1.9.
These APIs were new and documented as of Django 1.7: https://docs.djangoproject.com/en/1.7/ref/templates/api/#template-origin
Even in the 1.8 branch, there is no DeprecationWarning for this class: https://github.com/django/django/blob/stable/1.8.x/django/template/loader.py#L14
Change History (3)
comment:1 by , 10 years ago
| Cc: | added |
|---|---|
| Severity: | Normal → Release blocker |
comment:2 by , 10 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:3 by , 10 years ago
| Description: | modified (diff) |
|---|
May I ask about the use case so we can be sure to solve the issue appropriately? Thanks.
If possible we should restore the old aliases, after all this is a regression.