#2744 closed defect (fixed)
context processors cant return None cause it not checked in RequestContext
Reported by: | anonymous | Owned by: | Adrian Holovaty |
---|---|---|---|
Component: | Template system | Version: | |
Severity: | normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
this just came up in irc when someone did return None instead of a dict
Attachments (1)
Change History (3)
by , 18 years ago
Attachment: | context-processor-returns-none.patch added |
---|
comment:1 by , 18 years ago
Hmm.
I'm not sure if we should do this, or if we should make it extra-clear in the documentation that context processors must return a dictionary -- even if it's an empty dictionary.
comment:2 by , 18 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
my patch to fix it