#28606 closed Cleanup/optimization (fixed)
Deprecate CachedStaticFilesStorage
| Reported by: | Ed Morley | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.staticfiles | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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
Change History (7)
comment:1 by , 7 years ago
| Summary: | Mark CachedStaticFilesStorage as deprecated in Django 2.1 → Deprecate CachedStaticFilesStorage |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 5 years ago
| Has patch: | set |
|---|
comment:3 by , 5 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
PR