Opened 11 years ago
Closed 10 years ago
#19320 closed New feature (duplicate)
Ability to leverage cache key generation for cache templatetag
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Core (Cache system) | Version: | 1.4 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | yes |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Its currently not possible to leverage the code that generates a cache key in templatetag cache as its embedded inside django.templatetags.cache.CacheNode.render.
It would be useful to be able to generate these cache keys if you need to programatically delete them and it appears there are a number of gist's and other solutions floating around, but none of them are done in a DRY nature.
I propose that a method get_cache_key be part of the django.templatetags.cache module.
Change History (5)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:3 Changed 11 years ago by
| Has patch: | set |
|---|
pull request:
https://github.com/django/django/pull/541
comment:4 Changed 10 years ago by
| Needs documentation: | set |
|---|
As noted on the PR, this should be documented.
Note: See
TracTickets for help on using
tickets.
I've committed a fix for this in https://github.com/alexhayes/django/commit/0c8b693713dc4bd28bbdd4238b4294b4d310a66e
I'll be submitting a pull request shortly.