Opened 7 years ago

Last modified 7 years ago

#20423 assigned Bug

Template renderer does not parse numeric variables

Reported by: antonio@… Owned by: Deepak
Component: Template system Version: master
Severity: Normal Keywords: number variable
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: yes
Easy pickings: no UI/UX: no


Currently a Variable is defined, according to the django template manual, as :

Variable names consist of any combination of alphanumeric characters and the underscore ("_").

If a variable is composed of numbers only, it will not get its context data correctly, coming across as an int. This patch assigns the appropriate context data to the Variable class when it encounters an integer.

Here's the current behavior:

from django.template.base import Template
from django.template.base import Context
t = Template("{{ 123 }}")


t = Template("{{ foo }}")


Attachments (1)

number_templating.diff (515 bytes) - added by antonio@… 7 years ago.
Patch to assign context to numeric Variables in Django templating

Download all attachments as: .zip

Change History (7)

Changed 7 years ago by antonio@…

Attachment: number_templating.diff added

Patch to assign context to numeric Variables in Django templating

comment:1 Changed 7 years ago by anonymous

Definitely not full fix, it does cause regressions elsewhere - namely the view loading a changelist in the Admin.

comment:2 Changed 7 years ago by Simon Charette

The issue is valid but IMHO the code should be fixed to disallow such uses of number variables and the documentation fixed accordingly (e.g Variable name can't start with an integer).

I know this might be backward incompatible but I can't see any valid use case for this behavior, looks more like a side effect/oversight of the access by index feature. Am I missing something here?

comment:3 Changed 7 years ago by Simon Charette

Patch needs improvement: set
Triage Stage: UnreviewedAccepted

comment:4 Changed 7 years ago by Deepak

Owner: changed from nobody to Deepak
Status: newassigned

comment:5 Changed 7 years ago by Deepak

I totally agree with charettes that there may not be an use case for this. Hence, I'd propose to add warning first and then raise an exceptions if integer or float variable names are used. Does it makes sense?

comment:6 Changed 7 years ago by anonymous

Makes more sense as a doc ticket, agreed! Thanks for looking!


Note: See TracTickets for help on using tickets.
Back to Top