#33431: Regroup Violates Syntax Expectations
-------------------------------------------+-------------------------
               Reporter:  Caleb White      |          Owner:  nobody
                   Type:  Bug              |         Status:  new
              Component:  Template system  |        Version:  3.2
               Severity:  Normal           |       Keywords:  regroup
           Triage Stage:  Unreviewed       |      Has patch:  0
    Needs documentation:  0                |    Needs tests:  0
Patch needs improvement:  0                |  Easy pickings:  0
                  UI/UX:  0                |
-------------------------------------------+-------------------------
 I would like to re-report the following issue from 16 years ago:
 https://code.djangoproject.com/ticket/1461

 I hope that it is obvious why it would be useful to dynamically resolve
 this variable.

 I spent a long time trying to figure out why `group_key.grouper` was
 always `None` for me, and it's because the variable I'm using as the
 grouping token is being treated as a string rather than a variable.

 Honestly this seems like a serious design flaw in the template language
 itself - why are unquoted tokens ever treated as strings? How is the user
 of the template language supposed to know whether a given token will be
 resolved as a variable or treated as a literal string? This is very
 confusing and I can't find any explanation in the documentation of why
 this is the case. I can't think of any benefit gained by all of this
 ambiguity, so I imagine the only reason not to change this is going to be
 backwards compatibility.

 As far as I can tell, this bug is present in every version of Django.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33431>
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/049.0d36c3aea8a37a7dc5f5da111ed66315%40djangoproject.com.

Reply via email to