Opened 10 years ago
Closed 10 years ago
#23625 closed Cleanup/optimization (fixed)
Remove backwards compatibility CacheClass shim in cache backends
| Reported by: | Jaap Roes | Owned by: | Jaap Roes |
|---|---|---|---|
| Component: | Core (Cache system) | Version: | dev |
| Severity: | Normal | Keywords: | cacheclass compatibility |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
All cache backends, excluding memcached, have a CacheClass defined at the end of the file "For backwards compatibility". From what I can gather this means pre 1.3 compatibility.
The memcached backend has dropped this CacheClass (in 1.6 or 1.7). Does this mean all other cache backend can also drop this?
Change History (6)
comment:1 by , 10 years ago
| Summary: | Is CacheClass still needed "For backwards compatibility"? → Remove backwards compatibility CacheClass shim in cache backends |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
| Version: | 1.7 → master |
comment:2 by , 10 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 10 years ago
Should I put the note in internals/deprecation.txt (that's where the removal of django.core.cache.backends.memcached.CacheClass is mentioned) or releases/1.8.txt?
comment:4 by , 10 years ago
I would mention it as a backwards incompatible change in the 1.8 release notes.
comment:5 by , 10 years ago
| Has patch: | set |
|---|
comment:6 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
With a mention in the release notes it's probably fine.