#28606: Mark CachedStaticFilesStorage as deprecated in Django 2.1
------------------------------------------------+------------------------
Reporter: Ed Morley | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.staticfiles | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
`CachedStaticFilesStorage` has a number of drawbacks, and the docs in fact
already steer people away from using it:
https://docs.djangoproject.com/en/1.11/ref/contrib/staticfiles/#django.contrib.staticfiles.storage.CachedStaticFilesStorage
An additional problem is that `HashedFilesMixin` has had to make several
compromises in order to support `CachedStaticFilesStorage` which
unfortunately also impacts users of the recommended
`ManifestStaticFilesStorage` backend (see #28604). When these compromises
were added in #24452, it was suggested that `CachedStaticFilesStorage`
should just be deprecated/removed instead.
It's now too late to mark it as deprecated for Django 2.0, but we can do
so for Django 2.1 which would end up with its removal being in Django 3.0
all the same anyway.
I started this mailing list thread about the deprecation:
https://groups.google.com/forum/#!topic/django-developers/fmfQvuHBStk
--
Ticket URL: <https://code.djangoproject.com/ticket/28606>
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/051.94bebf4dc41cb588d0d79cac826b2b69%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
