Opened 9 years ago
Closed 9 years ago
#27847 closed New feature (wontfix)
Allow caching form templates when DEBUG=True
| Reported by: | Collin Anderson | Owned by: | nobody |
|---|---|---|---|
| Component: | Forms | Version: | 1.11 |
| 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 (last modified by )
Template-based widget rendering is super slow... can I add a CachedDjangoTemplates render?
Change History (3)
comment:1 by , 9 years ago
| Description: | modified (diff) |
|---|---|
| Type: | Uncategorized → New feature |
comment:2 by , 9 years ago
| Summary: | Cache Form Templates → Allow caching form templates when DEBUG=True |
|---|
comment:3 by , 9 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Ahh. Yes, I only tested the performance in development with debug=True. In that case I don't think it's worth adding this. I'll close the ticket.
Note:
See TracTickets
for help on using tickets.
Are you are having performance problems in development? If you didn't notice, in 1.11, "the cached template loader is now enabled if
DEBUGisFalseandOPTIONS['loaders']isn’t specified." That makes the proposed loader class only useful in development sinceDjangoTemplatesis equivalent toCachedDjangoTemplatesifDEBUG=False.