#23625: Is CacheClass still needed "For backwards compatibility"?
-------------------------------------+-------------------------------------
Reporter: jaap3 | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.7
Component: Core (Cache system) | Keywords: cacheclass
Severity: Normal | compatibility
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
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?
--
Ticket URL: <https://code.djangoproject.com/ticket/23625>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.cb75a7468e3d0aa91a1eefa91b06977e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
