#28782: Template variable resolution on objects that are no mappings but
implement
__getitem__
-------------------------------------+-------------------------------------
Reporter: Frank Sachsenheim | Owner: Frank
| Sachsenheim
Type: Bug | Status: assigned
Component: Template system | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
You're unlikely get a helpful response in this ticket tracker. You could
try a post to the DevelopersMailingList but I'm not sure if anyone who
worked on the template system in the early days of Django is still active.
I might be able to answer some of your questions by researching history
with `git blame` but I think you could do that just as well. It might be
helpful to see your work-in-progress code, also.
Given that the template system is over 10 years old, my gut says the risk
of regressions for this change is high and you might be better off
adapting your code to the current behavior. For example, maybe you could
wrap the objects in question in a class that will do the lookup that you
want.
--
Ticket URL: <https://code.djangoproject.com/ticket/28782#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.b1233c7aeb16674d0411b07b56fc624b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
